@friggframework/prettier-config
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Stale publisher change, 848d on npm, consistent with legitimate handoff not takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-standing stable publish, not removed by npm, indicates legitimate transfer. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): prettier is the tool being configured; it's a runtime dep, not directly imported in JS. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal config package in a large monorepo; low-value signals are structural, not malicious. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.2.2 | 1 / 0 | |
| 1.2.1 | 1 / 0 | |
| 1.2.0 | 1 / 0 | |
| 1.1.8 | 1 / 0 | |
| 1.1.7 | 1 / 0 | |
| 1.1.6 | 1 / 0 | |
| 1.1.5 | 1 / 0 | |
| 1.1.4 | 1 / 0 | |
| 1.1.3 | 1 / 0 | |
| 1.1.2 | 1 / 0 | |
| 1.0.6 | 0 / 1 | |
| 1.0.5 | 0 / 1 | |
| 1.0.3 | 0 / 1 | |
| 1.0.2 | 0 / 1 |
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsThis version was published by a different npm account (michael.webber.lefthook) than the most recent previously approved version (seanspeaks) on 2024-03-30. It has since remained available on npm for 848 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.