@buildtheearth/bot-utils
A utility library for the bots!
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): postinstall runs patch-package, a standard patching tool declared as a dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:patch-package | AI (phantom-deps): patch-package is used via postinstall script, not imported directly; false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 5 / 14 | |
| 1.0.5 | 5 / 14 | |
| 1.0.4 | 4 / 10 | |
| 1.0.3 | 4 / 10 | |
| 1.0.2 | 4 / 10 |
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.