@botonic/eslint-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eslint-plugin-jest | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-node | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-no-null | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-promise | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-prettier | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-filenames | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-simple-import-sort | AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.54.0 | 12 / 0 | |
| 0.53.0 | 12 / 0 | |
| 0.52.0 | 12 / 0 | |
| 0.51.0 | 12 / 0 | |
| 0.49.0 | 12 / 0 | |
| 0.48.0 | 12 / 0 | |
| 0.47.0 | 12 / 0 | |
| 0.46.0 | 12 / 0 | |
| 0.45.0 | 12 / 0 | |
| 0.44.0 | 12 / 0 | |
| 0.43.0 | 12 / 0 | |
| 0.42.0 | 12 / 0 | |
| 0.41.0 | 12 / 0 | |
| 0.40.0 | 12 / 0 | |
| 0.39.0 | 12 / 0 | |
| 0.38.0 | 12 / 0 | |
| 0.37.0 | 12 / 0 | |
| 0.36.0 | 12 / 0 | |
| 0.35.1 | 12 / 0 | |
| 0.35.0 | 12 / 0 | |
| 0.34.0 | 12 / 0 | |
| 0.33.0 | 12 / 0 | |
| 0.32.0 | 12 / 0 | |
| 0.31.0 | 12 / 0 | |
| 0.30.0 | 12 / 0 | |
| 0.29.0 | 12 / 0 | |
| 0.28.0 | 12 / 0 | |
| 0.27.1 | 12 / 0 | |
| 0.27.0 | 12 / 0 | |
| 0.26.0 | 12 / 0 |
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (oraventos) than the most recent previously approved version (mrabat) on 2025-04-01, but oraventos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mrabat) than the most recent previously approved version (oraventos) on 2025-02-18, but mrabat is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mrabat) than the most recent previously approved version (oraventos) on 2024-08-13, but mrabat is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (oraventos) than the most recent previously approved version (mrabat) on 2024-06-11, but oraventos is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.