@safe-global/protocol-kit
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer; no code changes, benign for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package without provenance; not a risk on its own. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 8.0.4 | 6 / 16 | |
| 8.0.3 | 6 / 16 | |
| 8.0.2 | 6 / 16 | |
| 8.0.1 | 6 / 16 | |
| 8.0.0 | 6 / 16 | |
| 7.2.0 | 6 / 14 | |
| 7.1.0 | 6 / 14 | |
| 7.0.0 | 6 / 14 | |
| 6.1.2 | 6 / 14 | |
| 5.2.27 | 6 / 14 | |
| 5.2.26 | 6 / 14 | |
| 5.2.25 | 6 / 14 | |
| 5.2.24 | 6 / 14 | |
| 5.2.23 | 6 / 14 | |
| 5.2.22 | 6 / 14 | |
| 5.2.21 | 6 / 14 | |
| 5.2.20 | 6 / 14 | |
| 5.2.19 | 6 / 14 |
v8.0.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zalens02.
v8.0.3
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: zalens02.
This version was published by a different npm account (zalens02) than the most recent previously approved version (yagopv) on 2026-07-09, but zalens02 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.
v8.0.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yagopv.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yagopv) than the most recent previously approved version (dasanra) on 2026-07-06, but yagopv 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.
v5.2.27
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 (zalens02) than the most recent previously approved version (dasanra) on 2026-04-17, but zalens02 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.