@nitra/eslint-config
An ESLint shareable config for projects using Vue and Node
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:graphql | AI (phantom-deps): graphql is listed as a direct dependency in package.json and referenced via graphql-eslint-anchor.js; phantom-dep is a false positive here. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 3.10.2 | 26 / 0 | |
| 3.10.1 | 26 / 0 | |
| 3.10.0 | 25 / 0 | |
| 3.9.5 | 26 / 0 | |
| 3.9.4 | 26 / 0 | |
| 3.9.3 | 26 / 0 | |
| 3.9.2 | 26 / 0 | |
| 3.9.1 | 26 / 0 | |
| 3.9.0 | 26 / 0 | |
| 3.8.1 | 26 / 0 | |
| 3.8.0 | 25 / 0 | |
| 3.7.0 | 25 / 0 | |
| 3.6.14 | 25 / 0 | |
| 3.6.13 | 25 / 0 | |
| 3.6.12 | 25 / 0 | |
| 3.6.11 | 25 / 0 | |
| 3.6.10 | 25 / 0 | |
| 3.6.9 | 24 / 0 | |
| 3.6.8 | 24 / 0 | |
| 3.6.7 | 24 / 0 | |
| 3.6.6 | 24 / 0 | |
| 3.6.4 | 24 / 0 | |
| 3.6.3 | 24 / 0 | |
| 3.6.2 | 24 / 0 | |
| 3.6.1 | 24 / 0 | |
| 3.6.0 | 24 / 0 | |
| 3.5.0 | 23 / 0 | |
| 3.4.8 | 22 / 0 | |
| 3.4.3 | 15 / 0 | |
| 3.4.2 | 15 / 0 | |
| 3.4.1 | 15 / 0 | |
| 3.4.0 | 15 / 0 | |
| 3.3.0 | 14 / 0 | |
| 3.2.3 | 13 / 0 | |
| 3.2.2 | 12 / 0 | |
| 3.2.1 | 11 / 0 | |
| 3.2.0 | 11 / 0 | |
| 3.1.7 | 11 / 0 | |
| 3.1.6 | 11 / 0 | |
| 3.0.11 | 14 / 0 | |
| 3.0.10 | 14 / 0 | |
| 3.0.9 | 14 / 0 | |
| 3.0.8 | 14 / 0 | |
| 3.0.7 | 14 / 0 | |
| 3.0.6 | 14 / 0 | |
| 3.0.5 | 14 / 0 | |
| 3.0.4 | 13 / 0 | |
| 3.0.3 | 13 / 0 | |
| 3.0.2 | 13 / 0 | |
| 3.0.1 | 13 / 0 | |
| 3.0.0 | 13 / 0 |
v3.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.