@reactionary/commercetools
This library was generated with [Nx](https://nx.dev).
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.10.4 | 5 / 1 | |
| 0.10.3 | 5 / 1 | |
| 0.10.2 | 5 / 2 | |
| 0.10.1 | 5 / 2 | |
| 0.10.0 | 5 / 2 | |
| 0.9.40 | 5 / 2 | |
| 0.9.39 | 5 / 2 | |
| 0.9.28 | 5 / 2 | |
| 0.9.27 | 5 / 2 | |
| 0.9.26 | 5 / 2 | |
| 0.9.25 | 5 / 2 | |
| 0.9.24 | 5 / 2 | |
| 0.9.23 | 5 / 2 | |
| 0.9.22 | 5 / 2 | |
| 0.9.21 | 5 / 2 | |
| 0.9.20 | 5 / 2 | |
| 0.9.19 | 5 / 2 | |
| 0.9.18 | 5 / 2 | |
| 0.9.17 | 5 / 2 | |
| 0.9.16 | 5 / 2 | |
| 0.9.15 | 5 / 2 | |
| 0.9.14 | 5 / 2 | |
| 0.9.13 | 5 / 2 | |
| 0.9.12 | 5 / 2 | |
| 0.9.11 | 5 / 2 |
v0.10.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.39
2 findingsPublished 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 (rogne) on 2026-07-03, 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.
v0.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.