@rumisle/pi-mom
Moved to @mariozechner/pi-mom
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Package is a documented migration stub pointing to @mariozechner/pi-mom; low-value signals are expected for this use case. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.70.1 | 0 / 0 | |
| 0.70.0 | 10 / 3 | |
| 0.68.2 | 10 / 3 | |
| 0.68.1 | 10 / 3 | |
| 0.68.0 | 10 / 3 | |
| 0.67.4 | 10 / 3 |
v0.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.