@sanity/message-protocol No license 22 versions

@sanity/message-protocol

npm Repository Homepage

22

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

sanity-svc.npmsanity-io

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
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	2026/05/06
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers have sanity-branded usernames consistent with internal team rotation.	ai	2026/05/06
maintainer-change	maintainer-removed	AI (maintainer-change): Removed maintainers also had sanity-branded names; consistent with internal team rotation, not takeover.	ai	2026/05/06
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy followed by org-level publisher migration is expected; no malicious code changes observed.	ai	2026/05/06

Versions (showing 22 of 22)

Version	Deps	Published
0.23.0	1 / 4	2026-04-14
0.19.0	1 / 4	2026-01-14
0.18.2	1 / 4	2026-01-12
0.18.1	1 / 4	2026-01-09
0.18.0	1 / 4	2025-12-23
0.17.8	1 / 3	2025-12-04
0.17.7	1 / 3	2025-12-01
0.17.6	1 / 3	2025-11-05
0.17.5	1 / 3	2025-10-28
0.17.4	1 / 3	2025-10-23
0.17.3	1 / 3	2025-10-22
0.17.2	1 / 3	2025-08-19
0.17.1	1 / 3	2025-08-13
0.17.0	1 / 3	2025-08-06
0.15.1	1 / 3	2025-07-11
0.15.0	1 / 3	2025-07-07
0.14.0	1 / 3	2025-06-12
0.13.3	1 / 3	2025-05-21
0.13.2	1 / 3	2025-05-16
0.13.1	1 / 3	2025-05-08
0.13.0	1 / 3	2025-05-06
0.12.0	1 / 3	2025-04-30

v0.23.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.19.0

2 findings

HIGH Publisher changed: sanity-io → sanity-svc.npm (on 2026-01-14) provenance

This version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.18.2

2 findings

HIGH Publisher changed: sanity-io → sanity-svc.npm (on 2026-01-12) provenance

This version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.18.1

2 findings

HIGH Publisher changed: sanity-io → sanity-svc.npm (on 2026-01-09) provenance

This version was published by a different npm account than previous versions on 2026-01-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.18.0

2 findings

HIGH Publisher changed: sanity-io → sanity-svc.npm (on 2025-12-23) provenance

This version was published by a different npm account than previous versions on 2025-12-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.17.8

2 findings

HIGH Publisher changed: sanity-io → sanity-svc.npm (on 2025-12-04) provenance

This version was published by a different npm account than previous versions on 2025-12-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.17.7

2 findings

HIGH Publisher changed: sanity-io → sanity-svc.npm (on 2025-12-01) provenance

This version was published by a different npm account than previous versions on 2025-12-01. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.17.6

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.17.5

1 finding

LOW No provenance attestation provenance

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

v0.17.4

1 finding

LOW No provenance attestation provenance

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

v0.17.3

1 finding

LOW No provenance attestation provenance

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

v0.17.2

1 finding

LOW No provenance attestation provenance

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

v0.17.1

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.15.1

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.3

1 finding

LOW No provenance attestation provenance

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

v0.13.2

1 finding

LOW No provenance attestation provenance

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

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.13.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.12.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.