← Home

@friggframework/eslint-config

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

Maintainers

michael.webber.lefthooklefthooktomseanspeaks

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Shared ESLint config: tiny config-only payload, short README, no keywords are inherent to this package type. ai
phantom-deps phantom-dep:eslint-plugin-json AI (phantom-deps): Same pattern: eslint config references plugins by name in config, not via require(). ai
phantom-deps phantom-dep:eslint-plugin-yaml AI (phantom-deps): Same pattern: eslint config references plugins by name in config, not via require(). ai
phantom-deps phantom-dep:@babel/eslint-parser AI (phantom-deps): Same pattern: eslint config references parsers by name in config, not via require(). ai
phantom-deps phantom-dep:eslint AI (phantom-deps): ESLint config packages reference plugins/parsers via config strings, not direct imports — stable FP for this package type. ai
phantom-deps phantom-dep:eslint-plugin-markdown AI (phantom-deps): Same pattern: eslint config references plugins by name in config, not via require(). ai
phantom-deps phantom-dep:eslint-plugin-no-only-tests AI (phantom-deps): Same pattern: eslint config references plugins by name in config, not via require(). ai
phantom-deps phantom-dep:eslint-config-prettier AI (phantom-deps): Same pattern: eslint config extends other configs by name, not via require(). ai

Versions (showing 13 of 13)

Version Deps Published
1.2.2 7 / 0
1.2.1 7 / 0
1.2.0 7 / 0
1.1.8 7 / 0
1.1.7 7 / 0
1.1.6 7 / 0
1.1.5 7 / 0
1.1.4 7 / 0
1.1.3 7 / 0
1.0.8 7 / 2
1.0.5 7 / 2
1.0.4 7 / 2
1.0.3 7 / 2

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

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

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

v1.1.6

1 finding
LOW No provenance attestation provenance

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

v1.1.5

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wprl-lh → seanspeaks (on 2023-01-09, known maintainer) provenance

This version was published by a different npm account (seanspeaks) than the most recent previously approved version (wprl-lh) on 2023-01-09, but seanspeaks is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wprl-lh → seanspeaks (on 2022-08-22, known maintainer) provenance

This version was published by a different npm account (seanspeaks) than the most recent previously approved version (wprl-lh) on 2022-08-22, but seanspeaks is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.4

1 finding
LOW No provenance attestation provenance

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

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