@abgov/adsp-service-sdk
Government of Alberta - SDK for ADSP platform and tenant services.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:moize | AI (dependencies): moize is a well-known memoization library; no malicious indicators, stable dependency for this SDK. | ai | |
| dependencies | unvetted-dep:express-http-context | AI (dependencies): express-http-context is a standard Express middleware; no malicious indicators, stable dependency for this SDK. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 2.24.0 | 23 / 0 | |
| 2.23.1 | 23 / 0 | |
| 2.23.0 | 23 / 0 | |
| 2.22.0 | 22 / 0 | |
| 2.21.0 | 22 / 0 | |
| 2.20.0 | 22 / 0 | |
| 2.19.0 | 22 / 0 | |
| 2.18.2 | 22 / 0 | |
| 2.18.1 | 22 / 0 | |
| 2.18.0 | 22 / 0 | |
| 2.17.0 | 22 / 0 | |
| 2.16.3 | 22 / 0 | |
| 2.16.2 | 22 / 0 | |
| 2.16.1 | 22 / 0 | |
| 2.16.0 | 22 / 0 | |
| 2.15.3 | 22 / 0 | |
| 2.15.2 | 22 / 0 | |
| 2.15.1 | 23 / 0 | |
| 2.14.0 | 23 / 0 | |
| 2.13.1 | 23 / 0 | |
| 2.13.0 | 23 / 0 | |
| 2.12.0 | 23 / 0 | |
| 2.11.0 | 21 / 0 | |
| 2.10.0 | 17 / 0 | |
| 2.9.2 | 17 / 0 | |
| 2.9.1 | 17 / 0 | |
| 2.9.0 | 17 / 0 | |
| 2.8.0 | 17 / 0 | |
| 2.7.0 | 17 / 0 | |
| 2.6.0 | 17 / 0 | |
| 2.5.0 | 17 / 0 | |
| 2.4.1 | 17 / 0 | |
| 2.4.0 | 17 / 0 | |
| 2.3.0 | 17 / 0 | |
| 2.2.2 | 17 / 0 | |
| 2.2.1 | 17 / 0 | |
| 2.2.0 | 17 / 0 |
v2.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.23.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.2
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 (dio.ting.zuge) on 2026-03-13, 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.9.1
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 (dio.ting.zuge) on 2026-02-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.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.