@santi020k/eslint-config-astro
Astro ESLint configuration
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Niche ESLint config package; sparse README and no keywords are cosmetic, not spam indicators. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.6.0 | 2 / 4 | |
| 1.5.0 | 2 / 4 | |
| 1.4.0 | 2 / 4 | |
| 1.3.0 | 2 / 4 | |
| 1.2.0 | 2 / 4 | |
| 1.1.0 | 2 / 4 | |
| 1.0.0 | 3 / 4 | |
| 0.8.1 | 2 / 3 | |
| 0.7.1 | 2 / 3 | |
| 0.7.0 | 2 / 3 | |
| 0.3.0 | 2 / 3 | |
| 0.2.0 | 2 / 3 | |
| 0.1.0 | 2 / 3 |
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.