@mindful-web/web-common
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
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.80.2 | 6 / 0 | |
| 1.80.0 | 6 / 0 | |
| 1.57.0 | 6 / 0 | |
| 1.28.0 | 6 / 0 | |
| 1.20.2 | 6 / 0 | |
| 1.11.9 | 6 / 0 | |
| 1.11.0 | 6 / 0 | |
| 1.0.0 | 6 / 0 |
v1.80.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.80.0
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 (brandonbk) than the most recent previously approved version (zarathustra323) on 2026-07-27, but brandonbk 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.20.2
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 (b77mills) than the most recent previously approved version (zarathustra323) on 2025-05-12, but b77mills 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.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
2 findingsThis version was published by a different npm account (brandonbk) than the most recent previously approved version (zarathustra323) on 2025-02-24. It has since remained available on npm for 509 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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.