@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 51 of 209)
| Version | Deps | Published |
|---|---|---|
| 14.451.4 | 4 / 0 | |
| 14.451.3 | 4 / 0 | |
| 14.451.2 | 4 / 0 | |
| 14.451.1 | 4 / 0 | |
| 14.451.0 | 4 / 0 | |
| 14.450.0 | 4 / 0 | |
| 14.449.0 | 4 / 0 | |
| 14.448.0 | 4 / 0 | |
| 14.447.2 | 4 / 0 | |
| 14.447.1 | 4 / 0 | |
| 14.447.0 | 4 / 0 | |
| 14.446.2 | 4 / 0 | |
| 14.446.1 | 4 / 0 | |
| 14.446.0 | 4 / 0 | |
| 14.445.2 | 4 / 0 | |
| 14.445.1 | 4 / 0 | |
| 14.445.0 | 4 / 0 | |
| 14.444.1 | 4 / 0 | |
| 14.444.0 | 4 / 0 | |
| 14.443.1 | 4 / 0 | |
| 14.443.0 | 4 / 0 | |
| 14.442.0 | 4 / 0 | |
| 14.441.0 | 4 / 0 | |
| 14.439.3 | 4 / 0 | |
| 14.439.2 | 4 / 0 | |
| 14.439.1 | 4 / 0 | |
| 14.439.0 | 4 / 0 | |
| 14.438.1 | 4 / 0 | |
| 14.438.0 | 4 / 0 | |
| 14.437.6 | 4 / 0 | |
| 14.437.5 | 4 / 0 | |
| 14.437.4 | 4 / 0 | |
| 14.437.3 | 4 / 0 | |
| 14.437.2 | 4 / 0 | |
| 14.437.1 | 4 / 0 | |
| 14.437.0 | 4 / 0 | |
| 14.436.0 | 4 / 0 | |
| 14.435.0 | 4 / 0 | |
| 14.434.0 | 4 / 0 | |
| 14.433.1 | 4 / 0 | |
| 14.433.0 | 4 / 0 | |
| 14.432.2 | 4 / 0 | |
| 14.432.1 | 4 / 0 | |
| 14.432.0 | 4 / 0 | |
| 14.431.0 | 4 / 0 | |
| 14.430.2 | 4 / 0 | |
| 14.430.1 | 4 / 0 | |
| 14.428.1 | 4 / 0 | |
| 14.428.0 | 4 / 0 | |
| 14.427.1 | 4 / 0 | |
| 14.416.0 | 4 / 0 |
v14.451.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.451.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.451.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.451.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.451.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.450.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.449.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.448.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.447.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.447.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.447.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.446.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.446.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.446.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.445.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.445.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.445.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.444.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.444.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.443.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.443.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.442.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.441.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.439.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.439.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.439.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.439.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.438.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.438.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.436.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.435.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.434.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.433.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.433.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.432.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.432.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.432.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.431.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.430.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.430.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.428.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.428.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.416.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.