← Home

@graphcommerce/eslint-config-pwa

4
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

paalesbramvanderholst

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@eslint/js AI (phantom-deps): ESLint config package; plugins loaded by convention, not direct import. ai
phantom-deps phantom-dep:typescript AI (phantom-deps): Peer/config dep for TypeScript ESLint integration; not directly imported. ai
phantom-deps phantom-dep:@eslint/compat AI (phantom-deps): ESLint config package; loaded by convention. ai
phantom-deps phantom-dep:@eslint/eslintrc AI (phantom-deps): ESLint config package; loaded by convention. ai
phantom-deps phantom-dep:eslint-config-prettier AI (phantom-deps): ESLint config package; referenced in config, not directly imported. ai
phantom-deps phantom-dep:eslint-import-resolver-typescript AI (phantom-deps): ESLint resolver; referenced in config, not directly imported. ai
phantom-deps phantom-dep:@graphcommerce/typescript-config-pwa AI (phantom-deps): Same-org sibling dep; expected pattern for this monorepo. ai

Versions (showing 4 of 4)

Version Deps Published
10.0.3 16 / 0
10.0.2 16 / 0
10.0.1 16 / 0
10.0.0 16 / 0

v10.0.3

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.

v10.0.2

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.

v10.0.1

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.

v10.0.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.