@kmamal/eslint-plugin-no-autofix
eslint-plugin-no-autofix
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Same-author scoped dependency, not an unrelated third-party package. | ai | |
| dependencies | unvetted-dep:@kmamal/find-up | AI (dependencies): Same-author scoped dependency; consistent with kmamal's package ecosystem pattern. | ai | |
| provenance | no-provenance | AI (provenance): Small ESLint plugin; lack of provenance is common and no other risk signals present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal ESLint plugin; sparse metadata is expected for a small utility, not a spam/malware indicator. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.0.10 | 0 / 0 | |
| 0.0.9 | 2 / 0 | |
| 0.0.8 | 2 / 0 | |
| 0.0.7 | 2 / 0 | |
| 0.0.6 | 2 / 0 | |
| 0.0.5 | 2 / 0 | |
| 0.0.4 | 2 / 0 | |
| 0.0.2 | 1 / 0 | |
| 0.0.1 | 1 / 0 |
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.