alint 0.22.1__py3-none-win_arm64.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- alint-0.22.1.data/scripts/alint.exe +0 -0
- alint-0.22.1.dist-info/METADATA +241 -0
- alint-0.22.1.dist-info/RECORD +8 -0
- alint-0.22.1.dist-info/WHEEL +4 -0
- alint-0.22.1.dist-info/licenses/LICENSE-APACHE +202 -0
- alint-0.22.1.dist-info/licenses/LICENSE-MIT +21 -0
- alint-0.22.1.dist-info/licenses/NOTICE +16 -0
- alint-0.22.1.dist-info/licenses/THIRD-PARTY-LICENSES.html +7736 -0
|
Binary file
|
|
@@ -0,0 +1,241 @@
|
|
|
1
|
+
Metadata-Version: 2.1
|
|
2
|
+
Name: alint
|
|
3
|
+
Version: 0.22.1
|
|
4
|
+
Summary: Lint repository structure, filenames, and file content with a fast, config-driven engine.
|
|
5
|
+
Home-page: https://alint.org
|
|
6
|
+
License: MIT OR Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://alint.org
|
|
8
|
+
Project-URL: Source, https://github.com/asamarts/alint
|
|
9
|
+
Project-URL: Documentation, https://alint.org/docs/
|
|
10
|
+
Requires-Python: >=3.7
|
|
11
|
+
Classifier: Development Status :: 5 - Production/Stable
|
|
12
|
+
Classifier: Environment :: Console
|
|
13
|
+
Classifier: Intended Audience :: Developers
|
|
14
|
+
Classifier: License :: OSI Approved :: MIT License
|
|
15
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
16
|
+
Classifier: Operating System :: POSIX :: Linux
|
|
17
|
+
Classifier: Operating System :: MacOS
|
|
18
|
+
Classifier: Operating System :: Microsoft :: Windows
|
|
19
|
+
Classifier: Topic :: Software Development :: Quality Assurance
|
|
20
|
+
Classifier: Topic :: Utilities
|
|
21
|
+
Description-Content-Type: text/markdown
|
|
22
|
+
|
|
23
|
+
# alint
|
|
24
|
+
|
|
25
|
+
[](https://crates.io/crates/alint)
|
|
26
|
+
[](https://github.com/asamarts/alint/actions/workflows/ci.yml)
|
|
27
|
+
[](#license)
|
|
28
|
+
|
|
29
|
+
**A fast, general linter.**
|
|
30
|
+
|
|
31
|
+
Code linters check what's inside a source file. alint checks the repository around it: files that should or shouldn't exist, naming conventions, file contents, values buried in `package.json`, `Cargo.toml` or a workflow YAML, and the relationships between files. The rules live in one `.alint.yml` and run on every pull request, in pre-commit and in your editor.
|
|
32
|
+
|
|
33
|
+
**Fast at scale:** the workspace-bundle benchmark checks 100,000 files in about 1.5 seconds and one million in under 20 seconds ([measured on every release](https://alint.org/benchmarks/)).
|
|
34
|
+
|
|
35
|
+
Every repository has a shape it is supposed to keep. Every package carries a README. Workflows pin their actions to a commit SHA. Nobody commits `target/` or `node_modules/`. Source files that need a license header have one. These rules are real, and a repo drifts when they slip, but they usually live in a reviewer's head or a line of `CONTRIBUTING.md`, where nothing fails when a pull request ignores them.
|
|
36
|
+
|
|
37
|
+
alint writes those rules down and enforces them. It takes over from [Repolinter](https://github.com/todogroup/repolinter) (archived in 2026), runs alongside ESLint, Clippy, or Ruff, and ships as a single static Rust binary with nothing to install at runtime.
|
|
38
|
+
|
|
39
|
+
<!-- Absolute URL on purpose: this README is also the crates.io and npm landing
|
|
40
|
+
page, and neither resolves relative image paths. The GIF is generated from
|
|
41
|
+
demo/alint.tape (via demo/render.sh), never hand-recorded, so it cannot
|
|
42
|
+
drift from real output.
|
|
43
|
+
|
|
44
|
+
width="880" is REQUIRED and is half the GIF's native 1760px. Most people
|
|
45
|
+
read GitHub on a HiDPI display, where a 1x asset gets upscaled 2x by the
|
|
46
|
+
browser and small antialiased terminal glyphs turn to mush. At 2x native,
|
|
47
|
+
HiDPI maps this 1:1 to device pixels (sharp) and 1x displays downscale it
|
|
48
|
+
exactly 2:1 (clean). Drop the attribute and the 1760px source blows out the
|
|
49
|
+
column; set it to 100% and the letters go blurry again. -->
|
|
50
|
+
<img src="https://raw.githubusercontent.com/asamarts/alint/main/demo/alint.gif" width="880" alt="alint finding structural violations in a repo, fixing the mechanical ones, and leaving the structural ones for a human">
|
|
51
|
+
|
|
52
|
+
*A tracked `target/`, an unpinned GitHub Action, a scratch planning doc at the repo root, and whitespace drift. alint finds all of it, fixes what is mechanical, and leaves what needs a decision. No per-language linter sees any of it.*
|
|
53
|
+
|
|
54
|
+
## Quickstart
|
|
55
|
+
|
|
56
|
+
```sh
|
|
57
|
+
# Install (Linux and macOS; Windows via npm, cargo, or the release tarball):
|
|
58
|
+
curl -fsSL https://alint.org/install.sh | bash
|
|
59
|
+
|
|
60
|
+
# Start from a few bundled rulesets:
|
|
61
|
+
cat > .alint.yml <<'YAML'
|
|
62
|
+
version: 1
|
|
63
|
+
extends:
|
|
64
|
+
- alint://bundled/oss-baseline@v1 # README, LICENSE, hygiene, merge markers
|
|
65
|
+
- alint://bundled/rust@v1 # auto-skips when there is no Rust
|
|
66
|
+
- alint://bundled/ci/github-actions@v1 # pin actions, least-privilege workflows
|
|
67
|
+
YAML
|
|
68
|
+
|
|
69
|
+
alint check # report what is wrong
|
|
70
|
+
alint fix --dry-run # preview the mechanical repairs
|
|
71
|
+
alint fix # apply them
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
`alint init` writes that file for you by detecting the ecosystems in your repo, so you rarely start from a blank page. The [quickstart on alint.org](https://alint.org/docs/getting-started/quickstart/) walks a first config end to end.
|
|
75
|
+
|
|
76
|
+
Ruleset authors can put versioned fixture documents under `alint-tests/` and run `alint test`.
|
|
77
|
+
Each test owns an isolated repository tree, config, environment, Git history, ordered check/fix
|
|
78
|
+
steps, inline expectations, and an optional JSON snapshot. The public
|
|
79
|
+
[`alint-testkit`](https://crates.io/crates/alint-testkit) crate exposes the same hermetic runner.
|
|
80
|
+
|
|
81
|
+
## How it works
|
|
82
|
+
|
|
83
|
+
A config is a list of rules, but you rarely write them all by hand. `extends:` composes **rulesets**, and alint ships 24 of them compiled into the binary, so there is no download and no network round trip. Most are gated on what the repo actually contains, so listing the Rust ruleset in a repo with no Rust does nothing. You layer your own rules on top, and override or switch off anything you inherit.
|
|
84
|
+
|
|
85
|
+
A rule is three things: a **kind** (the check to run, such as `file_exists`, `filename_case`, or `pair`), the **paths** it applies to, and a **severity**. There are 103 rule kinds across 13 families, plus 11 aliases. A rule can also carry a `when:` condition (run only on the default branch, or only when some file exists) and a `fix:`.
|
|
86
|
+
|
|
87
|
+
```yaml
|
|
88
|
+
# .alint.yml
|
|
89
|
+
version: 1
|
|
90
|
+
extends:
|
|
91
|
+
- alint://bundled/oss-baseline@v1
|
|
92
|
+
rules:
|
|
93
|
+
- id: no-focused-tests # a rule of your own, on top of the ruleset
|
|
94
|
+
kind: file_content_forbidden
|
|
95
|
+
paths: ["**/*.test.ts"]
|
|
96
|
+
pattern: '\.only\('
|
|
97
|
+
message: "Remove .only() so CI runs the whole suite, not one test"
|
|
98
|
+
level: error
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
Under the hood, alint walks the repository once, in parallel, honoring `.gitignore`, and reads each file's bytes at most once. The engine, the rules, the output formatters, and a language server for editors are all one binary, with no dynamically loaded plugins (an external tool can only be spawned per file by the opt-in, top-level-only `command` rule kind) and nothing from Node, the JVM, or Python in the path. The [concepts guide](https://alint.org/docs/concepts/) and [ARCHITECTURE.md](docs/design/ARCHITECTURE.md) go deeper.
|
|
102
|
+
|
|
103
|
+
## What it can check
|
|
104
|
+
|
|
105
|
+
The 103 rule kinds group into a handful of themes. The [rule reference](https://alint.org/docs/rules/) has every one with an example; a tour of the highlights:
|
|
106
|
+
|
|
107
|
+
- **Files and structure.** Require or forbid specific files and directories; cap file size, line count, directory depth, and files per directory; reject committed build output and OS junk.
|
|
108
|
+
- **Naming.** Filename case and regex conventions, with case-collision and reserved-name safety for cross-platform checkouts.
|
|
109
|
+
- **Content.** Required headers and footers, forbidden patterns such as merge markers or debug residue, and the everyday hygiene: trailing whitespace, final newlines, line endings, line width.
|
|
110
|
+
- **Config values.** Read into JSON, YAML, TOML, XML, dotenv, INI, `.properties`, and HCL with RFC 9535 JSONPath, then assert a value, match a pattern, forbid a key, or validate the whole file against a JSON Schema. Require `package.json` to declare a `license`, or every workflow to set `permissions: contents: read`.
|
|
111
|
+
- **Cross-file relationships.** The primitives most tools lack: `pair` (every `.proto` has its generated binding), `every_matching_has` (every `packages/*` has a README and a manifest), `unique_by` (no two crates share a name), `file_graph` (no import cycles or orphaned modules), `key_parity` (every locale file, or a local `.env`, declares the reference file's keys), and `generated_file_fresh` (a checked-in generated file still matches its source).
|
|
112
|
+
- **Security and encoding.** Immutable CI/container references across GitHub Actions, pre-commit, CircleCI, GitLab, Cloud Build, and Dockerfiles; Trojan-Source bidirectional controls, zero-width characters, byte-order marks, and text-encoding sanity.
|
|
113
|
+
- **Git hygiene.** Commit-message shape, sign-off and GPG signing, denied paths, and blame age.
|
|
114
|
+
- **Metadata.** Executable bits and shebangs, symlink and submodule policy, portable-filename checks.
|
|
115
|
+
|
|
116
|
+
When no kind fits, the `command` kind runs a tool you already trust and turns its exit code into a violation, so a one-off check still lives in the same config as everything else.
|
|
117
|
+
|
|
118
|
+
## Fixing, not just finding
|
|
119
|
+
|
|
120
|
+
Plenty of violations are mechanical: a missing final newline, a stray byte-order mark, an unsorted `CODEOWNERS`, a license header sitting above the shebang instead of below it. `alint fix` repairs those in place, with 26 ops covering content hygiene, structured-config edits, file and git operations, and list ordering. The ones that need a human decision it shows you or suggests, rather than guessing.
|
|
121
|
+
|
|
122
|
+
Each of the 26 auto-fix ops carries a safety tier, so a bare `alint fix` never surprises you:
|
|
123
|
+
|
|
124
|
+
- **Safe** fixes apply on a plain `alint fix`: whitespace and newline hygiene, line endings, header placement, sorting a marked block, reindentation.
|
|
125
|
+
- **Unsafe** fixes change meaning or remove content, so they wait for `alint fix --unsafe-fixes`: deleting a file, a regex `replace`, dropping a committed artifact from git's index. (As of v0.17, removing a file is Unsafe. A plain `alint fix` now *suggests* the deletion rather than doing it.)
|
|
126
|
+
- **Suggestions** are reported but never written, for violations with no mechanical repair.
|
|
127
|
+
|
|
128
|
+
Preview with `alint fix --dry-run`, or `alint fix --diff` for the exact edits. alint batches a file's edits in memory, writes each file once, and re-runs until the tree stops changing; a size limit (1 MiB by default) skips oversize files rather than rewriting them.
|
|
129
|
+
|
|
130
|
+
Because `extends:` can pull a ruleset from a URL, a fix that injects or remotely aims content (`replace`, `file_create`, `file_prepend`, and similar operations) from a remote or nested ruleset is demoted to a suggestion unless you list that source under `trusted_extends:`. The cap is applied to the effective fixer after field composition and template expansion, while a fix that shells out is refused from anywhere but your own top-level config. Every op is listed in the [rule reference](https://alint.org/docs/rules/).
|
|
131
|
+
|
|
132
|
+
## Adopt it without a flag day
|
|
133
|
+
|
|
134
|
+
You do not have to fix everything the first time alint runs. `alint baseline` records today's violations behind a content fingerprint, and `alint check --baseline` then passes on those and fails only on genuinely new ones. Turn it on as a blocking gate on day one and burn down the backlog on your own schedule, the way you would introduce a type checker to an untyped codebase.
|
|
135
|
+
|
|
136
|
+
## Where it runs
|
|
137
|
+
|
|
138
|
+
- **Pull requests.** The [`asamarts/alint` GitHub Action](https://alint.org/docs/integrations/github-actions/) annotates changed lines inline or uploads SARIF to Code Scanning, and `alint check --changed` lints only the files a PR touched.
|
|
139
|
+
- **Commits.** A [pre-commit](https://alint.org/docs/integrations/pre-commit/) hook (a prebuilt wheel, no toolchain) checks every commit; a manual `alint-fix` hook repairs on request.
|
|
140
|
+
- **Your editor.** `alint lsp` is a language server (diagnostics, hover-to-explain, apply-fix code actions), with marketplace extensions for VS Code and JetBrains, a source extension for Zed, and ready configs for Neovim, Sublime Text, Emacs, and Helix.
|
|
141
|
+
- **Coding agents.** The `agent` output format carries a per-violation instruction and fix command, and `alint export-agents-md` keeps the directives in `AGENTS.md` or `CLAUDE.md` in step with the rules alint enforces, so the agent and CI agree on the contract.
|
|
142
|
+
- **Any CI.** [8 output formats](https://alint.org/docs/reference/output-formats/) cover most pipelines: `human`, `json`, `sarif`, `github`, `markdown`, `junit`, `gitlab`, and `agent`. Exit codes are stable: `0` clean, `1` violations, `2` config error, `3` internal.
|
|
143
|
+
|
|
144
|
+
## Bundled rulesets
|
|
145
|
+
|
|
146
|
+
alint ships 24 bundled ecosystem rulesets inside the binary, pinned to the version you run and reachable as `alint://bundled/<name>@v1`. They group into:
|
|
147
|
+
|
|
148
|
+
- **Ecosystem baselines**, each gated so it is a no-op off-ecosystem: `rust`, `node`, `python`, `go`, `java`, `dotnet`, `php`, plus the always-on `oss-baseline` (the README / LICENSE / hygiene starting point, and a clean migration target for Repolinter).
|
|
149
|
+
- **Cross-file consistency**: `versioning` keeps release versions aligned across manifests, charts, API descriptions, and changelogs; `toolchain-pins` aligns exact Node, Rust, Python, Ruby, JVM, and .NET pins across local, Docker, and CI declarations.
|
|
150
|
+
- **Monorepo overlays**: a `monorepo` base plus `cargo-workspace`, `pnpm-workspace`, and `yarn-workspace` overlays that scope per-member checks to real package directories.
|
|
151
|
+
- **CI and tooling**: `ci/github-actions` (OpenSSF-guided workflow hardening), `tooling/editorconfig`, `docs/adr`, and the `hygiene/*` artifact and lockfile sets.
|
|
152
|
+
- **Compliance and governance**: `compliance/reuse`, `compliance/apache-2`, and `apache/governance` (the Apache TLP release discipline that arrow, spark, and airflow each re-implement by hand).
|
|
153
|
+
- **Agent-aware**: `agent-hygiene` (scratch docs, duplicate-versioned files, and debug residue that cluster in agent-authored commits) and `agent-context` (keeps `AGENTS.md` and friends honest).
|
|
154
|
+
|
|
155
|
+
Rulesets ship non-blocking by default: `info` or `warning` for recommendations, `error` only for unambiguous bugs. Redeclare a rule id in your own config to change its severity or scope, or set `level: off`. The [bundled-ruleset reference](https://alint.org/docs/bundled-rulesets/) lists every rule in each.
|
|
156
|
+
|
|
157
|
+
## On real repositories
|
|
158
|
+
|
|
159
|
+
alint ships [working configs for 30 open-source projects](https://alint.org/examples/), from single-language libraries to polyglot monorepos, each with a writeup of what alint catches that the project's own tooling misses. Writing them surfaced a few patterns that recur:
|
|
160
|
+
|
|
161
|
+
- Projects that lean on a convention without enforcing it. tokio has no validation scripts, yet its pipeline quietly assumes conventions alint can hold to.
|
|
162
|
+
- Projects drowning in hand-rolled verify scripts. Kubernetes maintains dozens of `hack/verify-*.sh`; the structural ones collapse into a handful of declarative rules.
|
|
163
|
+
- Projects with excellent code linters but no structural layer. ruff ships 900+ Python rules and still cannot check that its own internal crates keep `publish = false`.
|
|
164
|
+
- Polyglot trees no single per-language linter sees across: apache/arrow spans six languages, vercel/next.js is TypeScript and Rust, NixOS/nixpkgs is tens of thousands of files.
|
|
165
|
+
|
|
166
|
+
Start from the [example](https://alint.org/examples/) closest to your repo, or see [how alint compares](https://alint.org/compare/) with other tools and how to [migrate from Repolinter](https://alint.org/migrating-from/repolinter/).
|
|
167
|
+
|
|
168
|
+
## What alint is not
|
|
169
|
+
|
|
170
|
+
alint checks the shape and contents of a repository, not the semantics of the code inside it. It is deliberately not:
|
|
171
|
+
|
|
172
|
+
- a code or AST linter (use [ESLint](https://eslint.org/), [Clippy](https://doc.rust-lang.org/clippy/), [Ruff](https://docs.astral.sh/ruff/))
|
|
173
|
+
- a SAST scanner (use [Semgrep](https://semgrep.dev/), [CodeQL](https://codeql.github.com/))
|
|
174
|
+
- an IaC scanner (use [Checkov](https://www.checkov.io/), [Conftest](https://www.conftest.dev/))
|
|
175
|
+
- a full commit-message linter: the `git_commit_*` rule kinds cover basic shape checks (subject length and regex, sign-off, fixup commits), but for conventional-commit grammars, scopes and body/footer rules use [commitlint](https://commitlint.js.org/)
|
|
176
|
+
- a secret scanner (use [gitleaks](https://github.com/gitleaks/gitleaks), [TruffleHog](https://github.com/trufflesecurity/trufflehog))
|
|
177
|
+
|
|
178
|
+
It runs underneath those, and keeps its rules on the filesystem so they can keep theirs on the code.
|
|
179
|
+
|
|
180
|
+
## Install
|
|
181
|
+
|
|
182
|
+
```bash
|
|
183
|
+
# install.sh (Linux, macOS; x86_64 and aarch64)
|
|
184
|
+
curl -fsSL https://alint.org/install.sh | bash
|
|
185
|
+
|
|
186
|
+
# Homebrew (macOS, Linuxbrew)
|
|
187
|
+
brew install asamarts/alint/alint
|
|
188
|
+
|
|
189
|
+
# crates.io
|
|
190
|
+
cargo install alint
|
|
191
|
+
|
|
192
|
+
# npm (also puts alint on PATH; for Windows or a project-local dev dependency)
|
|
193
|
+
npm install -g @asamarts/alint
|
|
194
|
+
|
|
195
|
+
# PyPI (uvx / pipx / pip; the wheel embeds the binary, so no Python in the hot path)
|
|
196
|
+
uvx alint check
|
|
197
|
+
uv tool install alint
|
|
198
|
+
```
|
|
199
|
+
|
|
200
|
+
`install.sh` detects your platform, downloads the matching tarball, verifies its SHA-256, and installs to `~/.local/bin`. The npm and PyPI packages ship the same prebuilt binary inside per-platform packages, with no install script, so both work under `--ignore-scripts`, from offline mirrors, and on Windows (x64 and arm64). A distroless multi-arch Docker image is published to ghcr.io on every release:
|
|
201
|
+
|
|
202
|
+
```bash
|
|
203
|
+
docker run --rm -v "$PWD:/repo" ghcr.io/asamarts/alint:v0.22.1 check
|
|
204
|
+
```
|
|
205
|
+
|
|
206
|
+
Build from source with `cargo build --release -p alint`. Every channel and platform is covered in the [installation guide](https://alint.org/docs/getting-started/installation/).
|
|
207
|
+
|
|
208
|
+
alint is telemetry-free and makes no network access at runtime, except for the `extends:` URLs you write yourself, which must be SRI-pinned. The threat model is in [SECURITY.md](SECURITY.md).
|
|
209
|
+
|
|
210
|
+
## Documentation
|
|
211
|
+
|
|
212
|
+
[alint.org](https://alint.org) is the narrative home. The pages worth bookmarking:
|
|
213
|
+
|
|
214
|
+
- [Concepts](https://alint.org/docs/concepts/): the rule model, scopes, and `when:` conditions
|
|
215
|
+
- [Rule reference](https://alint.org/docs/rules/) and [bundled rulesets](https://alint.org/docs/bundled-rulesets/)
|
|
216
|
+
- [CLI](https://alint.org/docs/cli/) (all 13 subcommands) and the [configuration schema](https://alint.org/docs/configuration/)
|
|
217
|
+
- [Cookbook](https://alint.org/docs/cookbook/): monorepos, CI hardening, package shape, custom `command` rules
|
|
218
|
+
- [Architecture](https://alint.org/docs/about/architecture/) and [roadmap](https://alint.org/docs/about/roadmap/) through v1.0
|
|
219
|
+
|
|
220
|
+
In the repo: [CHANGELOG.md](CHANGELOG.md) for the per-version history, [docs/benchmarks/](docs/benchmarks/) for methodology and per-release results, and [SECURITY.md](SECURITY.md) for the threat model.
|
|
221
|
+
|
|
222
|
+
## Development
|
|
223
|
+
|
|
224
|
+
```bash
|
|
225
|
+
git clone https://github.com/asamarts/alint
|
|
226
|
+
cd alint
|
|
227
|
+
cargo test --workspace # Rust tests plus 578 declarative end-to-end policy tests
|
|
228
|
+
cargo run -- check # dogfood: alint lints its own repo
|
|
229
|
+
cargo bench -p alint-bench # criterion micro-benches
|
|
230
|
+
```
|
|
231
|
+
|
|
232
|
+
alint is a ten-crate Cargo workspace. Seven crates publish to crates.io: `alint` (the binary),
|
|
233
|
+
`alint-core` (the engine API), `alint-testkit` (the versioned policy-test model and hermetic
|
|
234
|
+
runner), plus the internal implementation crates `alint-dsl`, `alint-rules`, `alint-output`, and
|
|
235
|
+
`alint-lsp`. General policy tests live under `crates/alint-e2e/scenarios/`; bundled ruleset tests
|
|
236
|
+
live beside their owners under `crates/alint-dsl/ruleset-tests/v1/`. CLI snapshots run through
|
|
237
|
+
`trycmd`, and CI jobs use scripts under `ci/scripts/`.
|
|
238
|
+
|
|
239
|
+
## License
|
|
240
|
+
|
|
241
|
+
Dual-licensed under either [Apache License 2.0](LICENSE-APACHE) or the [MIT License](LICENSE-MIT), at your option. Unless you state otherwise, any contribution you submit for inclusion in alint is dual-licensed the same way, with no additional terms.
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
alint-0.22.1.data/scripts/alint.exe,sha256=iPpEkJHbw9cp6ixNhpbtvtVFcXmvpns61XuXVS6J-R4,19614720
|
|
2
|
+
alint-0.22.1.dist-info/METADATA,sha256=T-1G8-dVVTHUlsRHaBl6zULRkx-y0n_x8K2EPspq_vU,19315
|
|
3
|
+
alint-0.22.1.dist-info/WHEEL,sha256=P3BchSuE0ZroDrQhVjtqeC5MLadxSDtydsK2zGM_JB0,105
|
|
4
|
+
alint-0.22.1.dist-info/licenses/LICENSE-MIT,sha256=dskYibCnt7zr2tEUVO8qGxfGn-qr2vOntr2OVcSqYQU,1075
|
|
5
|
+
alint-0.22.1.dist-info/licenses/LICENSE-APACHE,sha256=z8d0m5b2O9McPEK1xHG_dWgUBT6EfBDz6wA0F7xSPTA,11358
|
|
6
|
+
alint-0.22.1.dist-info/licenses/NOTICE,sha256=vRgOOIKCxPv_wCr6wVd-D_PYF_gR286I2o-urDH_kXQ,615
|
|
7
|
+
alint-0.22.1.dist-info/licenses/THIRD-PARTY-LICENSES.html,sha256=FmctLPxY2jwjn4wog9cgxwPSWJ8SjcP1Vm-4tJuH4dU,392920
|
|
8
|
+
alint-0.22.1.dist-info/RECORD,,
|
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 alint contributors
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
alint
|
|
2
|
+
Copyright (c) 2026 alint contributors
|
|
3
|
+
|
|
4
|
+
This product is dual-licensed under either of
|
|
5
|
+
|
|
6
|
+
* Apache License, Version 2.0 (see LICENSE-APACHE), or
|
|
7
|
+
* MIT license (see LICENSE-MIT)
|
|
8
|
+
|
|
9
|
+
at your option.
|
|
10
|
+
|
|
11
|
+
alint's release binaries statically link third-party open-source crates. The
|
|
12
|
+
copyright notices and full license texts for those crates are published as the
|
|
13
|
+
THIRD-PARTY-LICENSES.html asset attached to each GitHub release
|
|
14
|
+
(https://github.com/asamarts/alint/releases), regenerated from the exact
|
|
15
|
+
dependency graph of that build. A CycloneDX software bill of materials
|
|
16
|
+
(alint.cdx.json) is attached to the same release.
|