@coveo/push-api-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): Coveo migrated publishing to GitHub Actions CI/CD with SLSA attestation; stable pattern for this org going forward. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): oa-npmcoveo is a Coveo org npm account; consistent with org-level CI/CD publishing migration. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainers consistent with org migrating to a shared CI/CD publishing account. | ai | |
| dependencies | unvetted-dep:@coveo/platform-client | AI (dependencies): First-party Coveo package; stable dependency across versions of this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.0.24 | 6 / 23 | |
| 4.0.23 | 6 / 23 | |
| 4.0.22 | 6 / 23 | |
| 4.0.21 | 6 / 23 | |
| 4.0.19 | 6 / 23 | |
| 4.0.17 | 6 / 23 | |
| 4.0.16 | 6 / 23 | |
| 4.0.15 | 6 / 23 | |
| 4.0.14 | 6 / 23 | |
| 4.0.13 | 6 / 23 | |
| 4.0.12 | 6 / 23 | |
| 4.0.11 | 6 / 23 |
v4.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.21
2 findingsThis version was published by a different npm account than previous versions on 2025-10-16. 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.
v4.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.