@genesislcap/eslint-config
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 — 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:eslint-config-google | AI (dependencies): eslint-config-google is a well-known Google-maintained ESLint config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-config-google | AI (phantom-deps): ESLint config packages reference deps in config files, not via import; phantom-dep is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): Same pattern — ESLint config references deps declaratively, not via import. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): Parser is referenced in ESLint config object, not imported directly; stable false positive. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): Resolver is referenced in ESLint config settings, not imported directly; stable false positive. | ai |
Versions (showing 26 of 234)
| Version | Deps | Published |
|---|---|---|
| 14.275.1 | 4 / 0 | |
| 14.275.0 | 4 / 0 | |
| 14.274.1 | 4 / 0 | |
| 14.274.0 | 4 / 0 | |
| 14.273.0 | 4 / 0 | |
| 14.272.0 | 4 / 0 | |
| 14.271.2 | 4 / 0 | |
| 14.271.1 | 4 / 0 | |
| 14.271.0 | 4 / 0 | |
| 14.270.0 | 4 / 0 | |
| 14.269.0 | 4 / 0 | |
| 14.268.4 | 4 / 0 | |
| 14.268.3 | 4 / 0 | |
| 14.268.2 | 4 / 0 | |
| 14.268.1 | 4 / 0 | |
| 14.268.0 | 4 / 0 | |
| 14.267.0 | 4 / 0 | |
| 14.266.1 | 4 / 0 | |
| 14.266.0 | 4 / 0 | |
| 14.265.1 | 4 / 0 | |
| 14.265.0 | 4 / 0 | |
| 14.264.4 | 4 / 0 | |
| 14.264.3 | 4 / 0 | |
| 14.264.2 | 4 / 0 | |
| 14.264.1 | 4 / 0 | |
| 14.264.0 | 4 / 0 |
v14.275.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.275.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.274.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.274.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.273.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.272.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.271.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.271.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.271.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.270.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.269.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.268.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.268.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.268.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.268.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.268.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.267.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.266.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.266.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.265.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.265.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.264.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.264.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.