@abinnovision/eslint-config-base
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eslint-plugin-unused-imports | AI (phantom-deps): ESLint config utilities loaded by convention, not direct imports. | ai | |
| phantom-deps | phantom-dep:typescript-eslint | AI (phantom-deps): ESLint config utilities loaded by convention, not direct imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): ESLint config utilities loaded by convention, not direct imports. | ai | |
| phantom-deps | phantom-dep:@vitest/eslint-plugin | AI (phantom-deps): ESLint config utilities loaded by convention, not direct imports. | ai | |
| phantom-deps | phantom-dep:globals | AI (phantom-deps): ESLint config utilities loaded by convention, not direct imports. | ai | |
| phantom-deps | phantom-dep:@eslint/js | AI (phantom-deps): ESLint config utilities loaded by convention, not direct imports. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped package with clear purpose from name and repo; missing description is stable pattern. | ai | |
| provenance | no-provenance | AI (provenance): Provenance adoption is sparse in ecosystem; not a disqualifier for established packages. | ai | |
| dependencies | unvetted-dep:@vitest/eslint-plugin | AI (dependencies): @vitest/eslint-plugin is a legitimate vitest ecosystem ESLint plugin; appropriate dependency for an eslint-config package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.4.0 | 7 / 6 | |
| 3.3.0 | 7 / 6 | |
| 3.2.2 | 7 / 6 | |
| 3.2.1 | 7 / 6 | |
| 3.2.0 | 7 / 6 | |
| 3.1.0 | 6 / 5 | |
| 3.0.0 | 6 / 5 |
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.