@transcend-io/utils
6
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
cami-transcendmichaelfarrell76bencmbrookdmattiaelidawson.turechekaldobarrhtunnicliff
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Still CI/CD attested via GitHub Actions; gitHead omission is benign CI metadata gap. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Org-scoped monorepo package; 0.0.0 is a common initial placeholder version for internal tooling, not a malware indicator here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 4 / 7 | |
| 0.1.3 | 4 / 7 | |
| 0.1.2 | 4 / 7 | |
| 0.1.1 | 4 / 7 | |
| 0.1.0 | 4 / 7 | |
| 0.0.0 | 3 / 6 |
v0.2.0
2 findings
HIGH
Missing gitHead — previous versions had it
provenance
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.