@buildeross/eslint-config-custom
Shared ESLint configuration for BuilderOSS apps
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-config-next | AI (phantom-deps): ESLint config packages reference presets in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-config-turbo | AI (phantom-deps): ESLint config packages reference presets in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): ESLint config packages reference presets in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-prettier | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): ESLint config packages reference parsers in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-unused-imports | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-simple-import-sort | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 0 / 10 | |
| 0.3.1 | 0 / 10 | |
| 0.3.0 | 0 / 10 | |
| 0.2.2 | 0 / 10 | |
| 0.2.1 | 0 / 10 | |
| 0.2.0 | 0 / 10 | |
| 0.1.3 | 9 / 0 | |
| 0.1.2 | 9 / 0 | |
| 0.1.1 | 9 / 0 | |
| 0.1.0 | 9 / 0 |
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.