@replayio/replay
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): text-table is a well-known, benign utility package appropriate for a CLI tool; no security concerns. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): The dynamic require loads only the package's own package.json to read its version — a standard, benign pattern stable across versions of this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool legitimately uses child_process for browser-launch auth flows; stable pattern across all versions of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped @replayio/ package with real repo, description, and ecosystem presence; mass-production signal is a false positive for this org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): replayio-release-bot is an established org bot with a clean track record (20 approved, 0 rejected); addition reflects legitimate org automation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of ryanjduffy is consistent with org-level transition to a release bot; no evidence of hostile takeover. | ai | |
| provenance | publisher-changed | AI (provenance): andarist is a highly trusted publisher (1979 approved packages, 9+ year history). Transition from ryanjduffy to andarist appears to be a legitimate maintainer handoff for the @replayio org. | ai | |
| dependencies | unvetted-dep:launchdarkly-node-client-sdk | AI (dependencies): Feature flagging SDK; common in production CLI tools for gradual feature rollouts. | ai | |
| phantom-deps | phantom-dep:is-uuid | AI (phantom-deps): Declared in dependencies; used in config files rather than direct imports. Benign pattern. | ai | |
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): Type-only package loaded by TypeScript convention; not directly imported at runtime. | ai | |
| dependencies | unvetted-dep:@replayio/sourcemap-upload | AI (dependencies): First-party Replay.io package; stable dependency for this organization's toolchain. | ai | |
| dependencies | unvetted-dep:winston-loki | AI (dependencies): Loki logging transport; expected for a telemetry-enabled CLI tool from Replay.io. | ai | |
| dependencies | unvetted-dep:is-uuid | AI (dependencies): Standard UUID validation utility; legitimate dependency for a recording management CLI tool. | ai | |
| dependencies | unvetted-dep:query-registry | AI (dependencies): npm registry querying utility; expected for a CLI tool that manages package recordings. | ai |
Versions (showing 51 of 93)
| Version | Deps | Published |
|---|---|---|
| 0.22.12 | 19 / 12 | |
| 0.22.11 | 18 / 11 | |
| 0.22.10 | 14 / 9 | |
| 0.22.9 | 14 / 9 | |
| 0.22.8 | 14 / 9 | |
| 0.22.7 | 14 / 9 | |
| 0.22.6 | 14 / 9 | |
| 0.22.5 | 14 / 9 | |
| 0.22.4 | 14 / 9 | |
| 0.22.3 | 14 / 9 | |
| 0.22.2 | 14 / 9 | |
| 0.22.1 | 14 / 9 | |
| 0.22.0 | 14 / 9 | |
| 0.21.7 | 14 / 9 | |
| 0.21.6 | 13 / 9 | |
| 0.21.5 | 13 / 9 | |
| 0.21.4 | 13 / 8 | |
| 0.21.3 | 13 / 8 | |
| 0.21.2 | 13 / 8 | |
| 0.21.1 | 13 / 8 | |
| 0.21.0 | 13 / 8 | |
| 0.20.1 | 13 / 8 | |
| 0.20.0 | 13 / 8 | |
| 0.19.4 | 10 / 8 | |
| 0.19.3 | 10 / 8 | |
| 0.19.2 | 10 / 8 | |
| 0.19.1 | 10 / 8 | |
| 0.19.0 | 10 / 8 | |
| 0.18.0 | 10 / 8 | |
| 0.17.5 | 10 / 8 | |
| 0.17.4 | 10 / 8 | |
| 0.17.3 | 10 / 8 | |
| 0.17.2 | 10 / 8 | |
| 0.17.1 | 10 / 8 | |
| 0.17.0 | 10 / 8 | |
| 0.16.1 | 10 / 8 | |
| 0.16.0 | 10 / 8 | |
| 0.15.0 | 10 / 8 | |
| 0.14.4 | 10 / 8 | |
| 0.14.3 | 10 / 8 | |
| 0.14.2 | 10 / 8 | |
| 0.14.1 | 10 / 8 | |
| 0.14.0 | 10 / 8 | |
| 0.13.1 | 10 / 8 | |
| 0.13.0 | 10 / 8 | |
| 0.12.13 | 10 / 8 | |
| 0.12.12 | 10 / 8 | |
| 0.12.11 | 10 / 8 | |
| 0.12.10 | 10 / 8 | |
| 0.12.8 | 10 / 7 | |
| 0.12.7 | 10 / 7 |
v0.22.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.11
2 findingsThis version was published by a different npm account than previous versions on 2024-07-03. 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.
v0.22.10
2 findingsThis version was published by a different npm account than previous versions on 2024-06-26. 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.
v0.22.9
2 findingsThis version was published by a different npm account than previous versions on 2024-06-25. 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.
v0.22.8
2 findingsThis version was published by a different npm account than previous versions on 2024-06-25. 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.
v0.22.7
2 findingsThis version was published by a different npm account than previous versions on 2024-06-19. 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.
v0.22.6
2 findingsThis version was published by a different npm account than previous versions on 2024-06-10. 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.
v0.22.5
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.
v0.22.4
2 findingsThis version was published by a different npm account than previous versions on 2024-05-08. 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.
v0.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.