@mindful-web/marko-web-mindful-ads
Mindful Ads Marko components for Mindful Web websites.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Org-published monorepo package; lack of provenance is consistent across all versions and not a malware indicator. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.63.0 | 3 / 0 | |
| 1.62.0 | 2 / 0 | |
| 1.58.0 | 2 / 0 | |
| 1.57.4 | 2 / 0 | |
| 1.57.3 | 2 / 0 | |
| 1.57.2 | 2 / 0 | |
| 1.57.0 | 2 / 0 | |
| 1.46.0 | 2 / 0 | |
| 1.45.1 | 2 / 0 | |
| 1.45.0 | 2 / 0 | |
| 1.22.0 | 2 / 0 |
v1.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.4
2 findings[Accepted risk] Package 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-16, 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.57.3
2 findings[Accepted risk] Package 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-16, 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.57.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
2 findings[Accepted risk] Package 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.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.