@coveo/relay
A library for sending analytics events using Coveo's Event protocol.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from individual (sssayegh) to Coveo org account (coveoit) reflects internal account consolidation. coveoit has 15 approved packages and strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers follow the *-coveo naming convention consistent with Coveo's internal npm accounts; routine team rotation for an established Coveo org package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers also follow Coveo naming patterns; combined with new Coveo-named maintainers, this is consistent with internal team changes, not a hostile takeover. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Package uses rollup to bundle output; uuid is a build-time bundled dependency, not directly imported in source. Benign pattern for this package. | ai | |
| phantom-deps | phantom-dep:@coveo/explorer-messenger | AI (phantom-deps): Same-org dependency bundled via rollup; not directly imported in source but used at build time. Benign pattern for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 2 / 17 | |
| 1.2.15 | 2 / 15 | |
| 1.2.14 | 2 / 15 | |
| 1.0.0 | 2 / 16 |
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
2 findingsThis version was published by a different npm account than previous versions on 2026-01-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.