← Home

eslint-config-standard-universal

npm

ESLint configuration for Standard, works universally with JavaScript, TypeScript, Svelte, and more. For browsers, Node.js, and Deno.

6
Versions
—
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

thaunknown

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:svelte AI (phantom-deps): Config package references svelte in ESLint config files, not via direct import; stable false positive. ai
phantom-deps phantom-dep:typescript AI (phantom-deps): Config package references typescript in ESLint config files, not via direct import; stable false positive. ai
phantom-deps phantom-dep:eslint-import-resolver-node AI (phantom-deps): Resolver referenced in config settings, not imported directly; stable false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
1.0.10 11 / 0
1.0.9 11 / 0
1.0.8 11 / 0
1.0.7 11 / 0
1.0.6 11 / 0
1.0.5 11 / 0

v1.0.10

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.0.9

1 finding
LOW No provenance attestation provenance

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

v1.0.8

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

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.0.5

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.