@adobe/mysticat-shared-seo-client
Shared modules of the SpaceCat Services - SEO Client
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Adobe @spacecat-shared packages publish via GitHub Actions CI with SLSA attestation; this is the expected automation pattern. | ai | |
| dependencies | unvetted-dep:@adobe/helix-universal | AI (dependencies): Internal Adobe dependency from the spacecat-shared ecosystem; stable pattern across Adobe packages. | ai | |
| dependencies | unvetted-dep:@adobe/spacecat-shared-utils | AI (dependencies): Internal Adobe spacecat-shared utility; consistent with this package's ecosystem context. | ai | |
| provenance | no-provenance | AI (provenance): Adobe publisher with established track record; missing provenance is common and not a risk signal here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.6.0 | 4 / 6 | |
| 1.5.1 | 4 / 6 | |
| 1.5.0 | 4 / 6 | |
| 1.4.0 | 4 / 6 | |
| 1.3.1 | 4 / 6 | |
| 1.3.0 | 4 / 6 | |
| 1.2.3 | 4 / 6 | |
| 1.2.2 | 4 / 6 | |
| 1.2.1 | 4 / 6 | |
| 1.2.0 | 4 / 6 | |
| 1.1.3 | 4 / 6 | |
| 1.1.2 | 4 / 6 | |
| 1.1.1 | 4 / 6 | |
| 1.1.0 | 4 / 6 | |
| 1.0.0 | 3 / 6 |
v1.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.