@adobe/spacecat-shared-drs-client
Shared modules of the Spacecat Services - Data Retrieval Service 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 org migrated publishing to GitHub Actions CI/CD; SLSA attestation confirms supply chain integrity for this package. | ai | |
| provenance | no-provenance | AI (provenance): Adobe org package; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.11.0 | 3 / 8 | |
| 1.10.0 | 3 / 8 | |
| 1.9.0 | 3 / 8 | |
| 1.8.1 | 3 / 8 | |
| 1.8.0 | 3 / 8 | |
| 1.7.2 | 3 / 8 | |
| 1.7.1 | 3 / 8 | |
| 1.7.0 | 3 / 8 | |
| 1.6.0 | 3 / 8 | |
| 1.5.0 | 1 / 8 | |
| 1.4.2 | 1 / 8 | |
| 1.4.1 | 1 / 8 | |
| 1.4.0 | 1 / 8 | |
| 1.3.1 | 1 / 8 | |
| 1.3.0 | 1 / 8 | |
| 1.2.0 | 1 / 8 | |
| 1.1.1 | 1 / 8 | |
| 1.1.0 | 1 / 8 | |
| 1.0.0 | 1 / 8 |
v1.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.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.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage 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.