lanekeep 0.3.2__py3-none-win_amd64.whl

lanekeep-0.3.2.dist-info/LICENSE-APACHE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

lanekeep-0.3.2.dist-info/LICENSE-MIT

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Fred Souza
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

lanekeep-0.3.2.dist-info/METADATA

@@ -0,0 +1,272 @@
+Metadata-Version: 2.1
+Name: lanekeep
+Version: 0.3.2
+Summary: Deterministic, AST-based architectural conformance checking
+License: MIT OR Apache-2.0
+Project-URL: Homepage, https://github.com/fmsouza/lanekeep
+Project-URL: Repository, https://github.com/fmsouza/lanekeep
+Project-URL: Changelog, https://github.com/fmsouza/lanekeep/blob/main/CHANGELOG.md
+Author: Fred Souza
+Author-email: 1396615+fmsouza@users.noreply.github.com
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Rust
+Classifier: Topic :: Software Development :: Quality Assurance
+Keywords: linter,static-analysis,tree-sitter,typescript,conformance
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+
+# lanekeep
+
+**Deterministic, AST-based architectural conformance checking for AI-generated and human-written code.**
+
+[![License: MIT OR Apache-2.0](https://img.shields.io/badge/license-MIT%20OR%20Apache--2.0-blue.svg)](#license)
+
+> **Status: early development.** Nothing is released yet and the CLI described below is not
+> usable. The architecture is settled — see [`docs/architecture.md`](docs/architecture.md) — and
+> the work is tracked as a sequence of milestones. Do not depend on this yet.
+
+---
+
+## What it is
+
+lanekeep is not a linter in the ESLint sense. ESLint enforces language-level correctness.
+lanekeep enforces *project-specific conventions* — the ones a language model has no way to infer
+from the code it is shown, because they live in your team's heads and your reviewers' comments.
+
+Every rule is a codified answer to **"the agent keeps doing this wrong."**
+
+Rules are TypeScript programs, written in the same language as the code they inspect:
+
+```ts
+import { defineRule } from 'lanekeep'
+
+export default defineRule({
+  id: 'local/no-numeric-sizes',
+  severity: 'error',
+
+  card: {
+    message: 'Literal numeric size inside makeStyles',
+    remediation: 'Use theme.spacing.*, theme.borderRadius.* or theme.borders.*',
+    examples: { bad: 'padding: 12', good: 'padding: theme.spacing.md' },
+  },
+
+  // Matched in Rust, at native speed. Your code runs only on matches.
+  query: `
+    (pair
+      key: (property_identifier) @prop
+      value: [(number) (unary_expression operand: (number))] @value) @match
+  `,
+
+  check(ctx, m) {
+    if (!/^(padding|margin|gap|borderRadius)/.test(ctx.text(m.prop))) return
+    if (Number(ctx.text(m.value)) === 0) return
+
+    const call = ctx.closestAncestor(m.match, '(call_expression function: (identifier) @f)')
+    if (!call) return
+    if (!ctx.resolvesToImport(call.f, { module: '@rneui/themed', name: 'makeStyles' })) return
+
+    ctx.report(m.match)
+  },
+})
+```
+
+`check` is ordinary TypeScript. Loop, accumulate state, build data structures, read other files,
+import shared helpers — there is no expressiveness ceiling and no DSL to learn beyond the query
+that gates it.
+
+## Why it exists
+
+An agent that writes code against your codebase will violate your conventions confidently and
+repeatedly, because those conventions are invisible in the code it was shown. Telling it again in
+the next prompt does not scale. Encoding the convention as a rule does.
+
+That makes the design constraints unusual for a static analyzer:
+
+- **It runs in the inner loop.** Agents and developers invoke it after every edit, so a cold run
+  on a couple of thousand files has a sub-second budget and a warm run has a sub-25ms one.
+- **Its output is read by a machine.** Violations are sorted deterministically, because an agent
+  that reads the output twice must not see reordering as change.
+- **Every rule carries its own fix.** `message`, `remediation` and `examples` are mandatory
+  fields, not documentation — they are the rule card that gets fed back to the agent.
+
+## How it stays fast with programmable rules
+
+The usual problem with a native tool that runs JavaScript plugins is the boundary between them:
+dispatching into JS once per AST node means tens of thousands of crossings per file.
+
+lanekeep dispatches once per **query match** instead. The tree-sitter query runs in Rust across a
+single shared parse; only matches reach your handler. That is typically two to three orders of
+magnitude fewer crossings, and it is the reason a Rust engine still earns its place once rules are
+TypeScript.
+
+```
+discover paths (globs, gitignore-aware)
+  └─> for each file, in parallel:
+        cache key ──hit──> validate tracked deps ──> cached violations + facts
+                  └─miss─> path and raw-text gates reject before any parse
+                           └─> parse ─> match queries in Rust
+                               └─> invoke the TypeScript handler, per match only
+  └─> reduce phase: cross-file rules consume facts only, never parse trees
+  └─> filter suppressions ─> sort ─> report
+```
+
+A warm run with no changes executes no JavaScript at all — every file is a cache hit.
+
+## Installation
+
+Pick whichever matches the project you are adding it to:
+
+```bash
+npm install --save-dev lanekeep      # Node
+pip install lanekeep                 # Python
+brew install fmsouza/tap/lanekeep    # macOS and Linux, system-wide
+cargo install lanekeep-cli           # from source
+```
+
+Or download a binary from the [releases page](https://github.com/fmsouza/lanekeep/releases).
+
+A single static binary with the JavaScript engine compiled in. **Neither Node.js nor Python is
+required to run lanekeep**, even though rules are written in TypeScript — a runtime is needed
+only to install it from that ecosystem's index, where it picks which binary to fetch. Nothing
+is pulled in as a dependency either way.
+
+Prebuilt for macOS on Apple silicon, Linux on x86-64 and arm64, and Windows on x86-64. The
+Linux binaries are built against glibc 2.17, so they run on anything from RHEL 7 onwards.
+Intel macOS is not prebuilt — `cargo install lanekeep-cli` builds it from source, and both the
+npm launcher and the Homebrew formula say so rather than failing obscurely.
+
+See [`docs/releasing.md`](docs/releasing.md) for how a release is cut.
+
+## What it looks like
+
+```
+$ lanekeep check
+src/also.ts:2:1 error [lanekeep/no-default-export] default export
+  → use a named export, so the symbol has one name every importer must use
+src/bad.ts:2:1 error [lanekeep/no-default-export] default export
+  → use a named export, so the symbol has one name every importer must use
+
+✖ 2 error(s) across 2 file(s) checked
+```
+
+Rules may offer a fix, applied with `--fix`:
+
+```
+$ lanekeep check --fix
+fixed 2 violation(s) in 2 file(s)
+```
+
+Only fixes a rule marked as behavior-preserving are applied. Anything else is a suggestion —
+shown, never written — because the cautious mistake costs a manual edit and the other one
+rewrites your code silently.
+
+Suppressions carry a mandatory reason and an optional expiry, and a directive that does not
+work says so — a missing reason, a bare rule id, or an unreadable date is reported rather
+than silently doing nothing:
+
+```ts
+// lanekeep-ignore-next-line lanekeep/no-default-export reason: legacy entry point
+export default parse
+```
+
+```
+$ lanekeep check --report-unused-suppressions
+```
+
+To start from nothing:
+
+```
+$ lanekeep init          # a config plus a first rule, both runnable
+```
+
+To find out where a run spent its time — the split says whether the query or the code is
+the problem:
+
+```
+$ lanekeep check --profile
+```
+
+To find out what a rule wants without opening its source:
+
+```
+$ lanekeep explain lanekeep/no-default-export
+$ lanekeep rules --json
+```
+
+For fast feedback on what you touched:
+
+```
+$ lanekeep check --staged     # what is about to be committed
+$ lanekeep check --since main # what changed against a ref
+```
+
+Both are intersected with the config's `include`/`exclude`, and both skip cross-file rules —
+a whole-corpus rule over a subset gives a wrong answer, not a smaller one, so they are
+skipped and named on stderr rather than quietly producing one.
+
+Exit `0` when clean, `1` when violations are found, `2` when the checker could not run —
+a caller has to be able to tell "your code has problems" from "the tool is broken".
+Four output formats: `human` (default), `json` (versioned, stable schema), `sarif` (GitHub
+code scanning), and `agent` — token-minimal, grouped by rule rather than by file, with each
+rule's card stated once instead of once per violation. Diagnostics always go to stderr, so
+piping into a parser works even when something fails.
+
+## Documentation
+
+| Document | Purpose |
+| --- | --- |
+| [`docs/architecture.md`](docs/architecture.md) | The full design: execution model, host API, cache, milestones |
+| [`docs/built-in-rules.md`](docs/built-in-rules.md) | The rules lanekeep ships with, and their options |
+| [`docs/cross-file-rules.md`](docs/cross-file-rules.md) | Writing a rule that needs a whole-corpus view |
+| [`AGENTS.md`](AGENTS.md) | How to work in this repository — for coding agents and humans alike |
+| [`CONTRIBUTING.md`](CONTRIBUTING.md) | Setup, commands, and the pull request process |
+| [`SECURITY.md`](SECURITY.md) | Threat model and how to report a vulnerability |
+| [`docs/releasing.md`](docs/releasing.md) | How a release is built, gated and published |
+
+## Security
+
+lanekeep is meant to run as a pre-commit hook and inside CI, which makes it a supply-chain target.
+Rules are executable code, so the posture is about confinement rather than absence:
+
+- **No ambient authority.** Rules run in an embedded QuickJS sandbox and reach exactly the host
+  functions lanekeep exposes. `fs`, `process`, `child_process`, network and dynamic import are not
+  restricted — they do not exist in the context.
+- **No network access.** Ever, in any mode, with no configuration that enables it.
+- **Filesystem confinement.** Reads go through a tracked `ctx.readFile`, confined to the project
+  root. Writes happen only under `--fix`, only to matched files, only within reported ranges.
+- **Bounded execution.** A per-invocation timeout, a 15-second global run budget and a per-runtime
+  memory ceiling, none disableable — a rule that hangs a pre-commit hook is indistinguishable from
+  a broken tool. Breaching any of them cancels the run and exits `2`, rather than reporting a
+  partial result as a clean one.
+- **Deterministic by construction.** The sandbox withholds the clock and randomness, so a rule
+  cannot introduce nondeterminism even by accident.
+
+This bounds blast radius and makes third-party rule sets reviewable. It is not a boundary against
+someone who can already commit to the repository being checked. To report a vulnerability, see
+[`SECURITY.md`](SECURITY.md).
+
+## Contributing
+
+Contributions are welcome, particularly new built-in rules and new host API surface. Start
+with [`CONTRIBUTING.md`](CONTRIBUTING.md) — `./scripts/setup-dev.sh` installs everything and
+wires the git hooks.
+
+All work ships as squashed pull requests with [Conventional Commits](https://www.conventionalcommits.org/)
+titles. `main` is protected and takes no direct pushes.
+
+## License
+
+Licensed under either of
+
+- Apache License, Version 2.0 ([`LICENSE-APACHE`](LICENSE-APACHE) or
+  <http://www.apache.org/licenses/LICENSE-2.0>)
+- MIT License ([`LICENSE-MIT`](LICENSE-MIT) or <http://opensource.org/licenses/MIT>)
+
+at your option.
+
+Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in
+this work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without
+any additional terms or conditions.

lanekeep-0.3.2.dist-info/RECORD

@@ -0,0 +1,6 @@
+lanekeep-0.3.2.data/scripts/lanekeep.exe,sha256=ox9s5iyNS-EpwcBc6wbZR6gZLx3cn4C2ucBH238FR5U,9084416
+lanekeep-0.3.2.dist-info/METADATA,sha256=2sUb-wTMWIvz1AydZ4pUM09ZdFH5R838Gfcs1xm_uoI,11623
+lanekeep-0.3.2.dist-info/WHEEL,sha256=SwdbcD4j93yZQoCopuduhrN17bTvD32gIB2uc8vzito,109
+lanekeep-0.3.2.dist-info/LICENSE-MIT,sha256=hvR8c5Dq0PDrzBI3n19ahl5w9YynDeo4Nqzgwb4jCpA,1067
+lanekeep-0.3.2.dist-info/LICENSE-APACHE,sha256=z8d0m5b2O9McPEK1xHG_dWgUBT6EfBDz6wA0F7xSPTA,11358
+lanekeep-0.3.2.dist-info/RECORD,,

lanekeep-0.3.2.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: lanekeep build-python-wheels.sh
+Root-Is-Purelib: false
+Tag: py3-none-win_amd64