@williamthorsen/eslint-config-typescript
ESLint config for TypeScript, JSON & YML
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:globals | AI (phantom-deps): ESLint config packages reference plugins/parsers in config, not code; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-n | AI (phantom-deps): ESLint config packages reference plugins/parsers in config, not code; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-yml | AI (phantom-deps): ESLint config packages reference plugins/parsers in config, not code; stable pattern. | ai | |
| phantom-deps | phantom-dep:yaml-eslint-parser | AI (phantom-deps): ESLint config packages reference plugins/parsers in config, not code; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-jsonc | AI (phantom-deps): ESLint config packages reference plugins/parsers in config, not code; stable pattern. | ai | |
| phantom-deps | phantom-dep:jsonc-eslint-parser | AI (phantom-deps): ESLint config packages reference plugins/parsers in config, not code; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-promise | AI (phantom-deps): ESLint config packages reference plugins/parsers in config, not code; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-unicorn | AI (phantom-deps): ESLint config packages reference plugins/parsers in config, not code; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-package-json | AI (phantom-deps): ESLint config packages reference plugins/parsers in config, not code; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-eslint-comments | AI (phantom-deps): ESLint config packages reference plugins/parsers in config, not code; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-simple-import-sort | AI (phantom-deps): ESLint config packages reference plugins/parsers in config, not code; stable pattern. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.17.6 | 12 / 10 | |
| 5.17.5 | 12 / 10 | |
| 5.17.4 | 12 / 10 | |
| 5.17.3 | 12 / 10 | |
| 5.17.2 | 12 / 10 | |
| 5.17.1 | 12 / 10 | |
| 5.16.2 | 12 / 10 | |
| 5.16.1 | 12 / 10 | |
| 5.14.0 | 12 / 10 | |
| 5.13.0 | 12 / 10 | |
| 5.12.4 | 12 / 10 | |
| 5.12.3 | 12 / 10 |
v5.17.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.17.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.17.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.