@replayio/test-utils
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (undici, winston, fs-extra, winston-loki) are all well-established, legitimate packages consistent with test recording/logging functionality for Replay.io. | ai | |
| provenance | publisher-changed | AI (provenance): andarist is a highly established npm publisher (3286 days, 2082 approved packages) taking over from ryanjduffy on the replayio org — consistent with a legitimate maintainer transition. | ai | |
| dependencies | unvetted-dep:winston-loki | AI (dependencies): winston-loki is a standard Loki logging transport for winston; legitimate use in a logging-capable test utility package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard JWT/auth token payload decoding pattern in auth.ts; not a malicious payload — it's parsing a base64-encoded token passed as input. | ai | |
| dependencies | unvetted-dep:launchdarkly-node-client-sdk | AI (dependencies): LaunchDarkly's official Node.js SDK; legitimate use for feature flagging in Replay.io's test utilities. | ai | |
| dependencies | unvetted-dep:query-registry | AI (dependencies): query-registry is a legitimate npm registry query library; appropriate for a test-utils package that checks package versions. | ai | |
| dependencies | unvetted-dep:mixpanel | AI (dependencies): Mixpanel is a well-known analytics SDK; its use in a test-utils package for telemetry is legitimate and expected. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.0.7 | 17 / 7 | |
| 3.0.5 | 9 / 5 | |
| 3.0.4 | 9 / 5 | |
| 3.0.3 | 9 / 4 | |
| 3.0.2 | 9 / 4 | |
| 3.0.1 | 5 / 4 | |
| 3.0.0 | 5 / 4 | |
| 2.1.1 | 5 / 4 | |
| 2.1.0 | 5 / 4 | |
| 2.0.2 | 5 / 4 | |
| 2.0.1 | 5 / 4 | |
| 2.0.0 | 5 / 4 |
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
2 findingsThis version was published by a different npm account than previous versions on 2024-05-17. 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.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.