← Home

@santi020k/eslint-config-expo

npm Repository Homepage

Expo ESLint configuration

13
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

santi020k

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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

Versions (showing 13 of 13)

Version Deps Published
2.1.0 4 / 3
2.0.0 4 / 3
1.6.0 4 / 4
1.5.0 4 / 4
1.3.0 4 / 4
1.0.0 4 / 4
0.8.1 4 / 3
0.7.1 5 / 3
0.7.0 5 / 3
0.2.2 5 / 3
0.2.1 5 / 3
0.2.0 5 / 3
0.1.0 5 / 3

v0.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.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.