@alexlit/config-npmlint
npmlint config
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established publisher with clean track record; config-only package with no code changes — dormancy is low risk here. | ai | |
| dependencies | unvetted-dep:lockfile-lint | AI (dependencies): lockfile-lint is a well-known linting tool; expected peer dep for this config package. | ai | |
| dependencies | unvetted-dep:npm-package-json-lint-config-default | AI (dependencies): npm-package-json-lint-config-default is a standard companion config; appropriate for this package's purpose. | ai | |
| phantom-deps | phantom-dep:lockfile-lint | AI (phantom-deps): Config-only package; deps are referenced in config files, not imported directly. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:npm-package-json-lint | AI (phantom-deps): Config-only package; deps are referenced in config files, not imported directly. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:npm-package-json-lint-config-default | AI (phantom-deps): Config-only package; deps are referenced in config files, not imported directly. Stable pattern for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 9.2.0 | 3 / 0 | |
| 9.1.1 | 3 / 0 | |
| 9.1.0 | 3 / 0 | |
| 9.0.0 | 3 / 0 | |
| 8.0.0 | 3 / 0 | |
| 7.1.0 | 3 / 0 |
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.