@sanity/logos
Supply chain provenance
Status for the latest visible version.
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): gitHead dropped due to CI/CD trusted-publisher move; provenance attestation present instead. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sanity-svc.npm is the org's service account for automated publishing. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer list consolidated to service account under trusted publisher; legitimate org transition. | ai | |
| typosquat | typosquat.levenshtein:log4js | AI (typosquat): Scoped @sanity/logos package is unrelated to log4js; Levenshtein match is a false positive for this established Sanity.io package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.2.4 | 1 / 8 | |
| 2.2.3 | 1 / 8 | |
| 2.2.2 | 1 / 23 | |
| 2.2.1 | 0 / 24 | |
| 2.2.0 | 0 / 47 | |
| 2.1.13 | 0 / 47 | |
| 2.1.12 | 0 / 47 |
v2.2.4
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[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: GitHub Actions.
v2.2.3
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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (sanity-io) on 2026-07-22, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v2.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.