← Home

@sanity/message-protocol

npm Repository Homepage
33
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

sanity-svc.npmsanity-io

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): sanity-svc.npm is a Sanity org service account with strong approval history; publisher change reflects org-level migration. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers have sanity-branded usernames consistent with internal team rotation. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers also had sanity-branded names; consistent with internal team rotation, not takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by org-level publisher migration is expected; no malicious code changes observed. ai

Versions (showing 33 of 33)

Version Deps Published
0.23.0 1 / 4
0.19.0 1 / 4
0.18.2 1 / 4
0.18.1 1 / 4
0.18.0 1 / 4
0.17.8 1 / 3
0.17.7 1 / 3
0.17.6 1 / 3
0.17.5 1 / 3
0.17.4 1 / 3
0.17.3 1 / 3
0.17.2 1 / 3
0.17.1 1 / 3
0.17.0 1 / 3
0.15.1 1 / 3
0.15.0 1 / 3
0.14.0 1 / 3
0.13.3 1 / 3
0.13.2 1 / 3
0.13.1 1 / 3
0.13.0 1 / 3
0.12.0 1 / 3
0.11.0 1 / 3
0.10.0 1 / 3
0.9.0 1 / 3
0.8.0 1 / 3
0.7.0 1 / 3
0.6.0 1 / 3
0.5.0 1 / 3
0.4.0 1 / 3
0.3.0 1 / 3
0.2.0 1 / 3
0.1.0 1 / 3

v0.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.