@santi020k/eslint-config-expo
Expo ESLint configuration
4
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
santi020k
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:cross-dirname | AI (dependencies): cross-dirname is a small utility for ESM __dirname compatibility; expected in an ESM ESLint config package. | ai | |
| dependencies | unvetted-dep:eslint-config-expo | AI (dependencies): eslint-config-expo is the official Expo ESLint config; its use here is the core purpose of this wrapper package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped ESLint config package; sparse README is typical for this category, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:eslint-config-expo | AI (phantom-deps): eslint-config-expo is a runtime dep used via config composition, not direct import; phantom-dep is a false positive here. | ai |
v1.6.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.