@mindful-web/marko-web-p1-events
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 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.80.0 | 5 / 0 | |
| 1.79.5 | 5 / 0 | |
| 1.79.1 | 5 / 0 | |
| 1.79.0 | 5 / 0 | |
| 1.76.5 | 5 / 0 | |
| 1.76.4 | 5 / 0 | |
| 1.76.3 | 5 / 0 | |
| 1.76.2 | 5 / 0 | |
| 1.76.1 | 5 / 0 | |
| 1.76.0 | 5 / 0 | |
| 1.75.0 | 5 / 0 | |
| 1.64.3 | 5 / 0 | |
| 1.57.0 | 5 / 0 | |
| 1.56.1 | 3 / 0 | |
| 1.56.0 | 3 / 0 | |
| 1.45.0 | 3 / 0 | |
| 1.33.2 | 3 / 0 | |
| 1.23.0 | 3 / 0 | |
| 1.13.0 | 3 / 0 | |
| 1.11.9 | 3 / 0 | |
| 1.11.5 | 3 / 0 | |
| 1.0.1 | 3 / 0 | |
| 1.0.0 | 3 / 0 |
v1.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.79.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.79.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.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 (zarathustra323) than the most recent previously approved version (brandonbk) on 2026-03-15, but zarathustra323 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.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.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 (solocommand) on 2025-11-06, 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.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.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 2025-06-04, 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.13.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 (b77mills) than the most recent previously approved version (zarathustra323) on 2025-03-19, 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.5
2 findingsThis version was published by a different npm account (b77mills) than the most recent previously approved version (zarathustra323) on 2025-03-03. It has since remained available on npm for 502 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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.