← Home

@arcgis/eslint-config

npm

ESLint configuration for arcgis-web-components

7
Versions
SEE LICENSE IN LICENSE.md
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

odoeffaubrydpaddockdan11669twesterhuys

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@types/confusing-browser-globals AI (dependencies): @types/confusing-browser-globals is a benign type-definition package with no runtime risk; stable false positive for this package. ai
bogus-package bogus-package AI (bogus-package): Scoped corporate ESLint config; sparse metadata is typical for internal tooling packages. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit runtime dependency for TypeScript-compiled packages; stable false positive. ai
phantom-deps phantom-dep:jsonc-eslint-parser AI (phantom-deps): Referenced in ESLint config files by convention, not directly imported; stable false positive for this package. ai
phantom-deps phantom-dep:@types/confusing-browser-globals AI (phantom-deps): Type-only package loaded by framework convention; stable false positive for this ESLint config. ai

Versions (showing 7 of 7)

Version Deps Published
5.0.19 13 / 0
5.0.18 13 / 0
5.0.17 13 / 0
5.0.16 13 / 0
5.0.12 13 / 0
4.34.8 10 / 0
4.34.7 10 / 0

v5.0.19

1 finding
LOW No provenance attestation provenance

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

v5.0.12

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.

v4.34.8

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.

v4.34.7

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.