@amplitude/plugin-session-replay-browser
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@amplitude/analytics-client-common | AI (phantom-deps): Same-org internal dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@amplitude/analytics-core | AI (phantom-deps): Same-org internal dependency; stable pattern for this package. | ai | |
| source-diff | obfuscated-file-transition:lib/scripts/observers-min.js | AI (source-diff): Rollup/terser minified build output with sourcemaps, not obfuscation; stable for this package. | ai | |
| dependencies | unvetted-dep:@amplitude/rrweb-plugin-console-record | AI (dependencies): Same-org Amplitude dependency used in session replay; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@amplitude/rrweb-record | AI (dependencies): Same-org Amplitude dependency used in session replay; stable pattern across versions. | ai | |
| source-diff | encoded-string-file:lib/scripts/plugin-session-replay-browser-esm.js | AI (source-diff): Standard minified TypeScript bundle output; samples show normal TS helpers, not obfuscated payloads. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; missing gitHead reflects CI config change, not integrity loss. | ai | |
| source-diff | encoded-string-file:lib/scripts/plugin-session-replay-browser-min.js | AI (source-diff): Minified SDK bundle; long encoded strings are expected build artifacts for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Fires on minified session-replay bundle; expected pattern for this package, not malicious obfuscation. | ai | |
| phantom-deps | phantom-dep:@amplitude/rrweb-plugin-console-record | AI (phantom-deps): First-party @amplitude dep bundled into output; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@amplitude/rrweb-record | AI (phantom-deps): First-party @amplitude dep bundled into output; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:idb-keyval | AI (phantom-deps): idb-keyval is a declared runtime dep; phantom-dep heuristic false positive for this bundled package. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Fires on minified bundle; Reflect.get in minified code is a standard JS pattern, not evasion. | ai |
Versions (showing 89 of 189)
| Version | Deps | Published |
|---|---|---|
| 1.20.2 | 4 / 11 | |
| 1.20.1 | 4 / 11 | |
| 1.20.0 | 4 / 11 | |
| 1.19.3 | 4 / 11 | |
| 1.19.2 | 4 / 11 | |
| 1.19.1 | 4 / 11 | |
| 1.19.0 | 4 / 11 | |
| 1.18.2 | 4 / 11 | |
| 1.18.1 | 4 / 11 | |
| 1.18.0 | 4 / 11 | |
| 1.17.0 | 4 / 11 | |
| 1.16.15 | 4 / 11 | |
| 1.16.14 | 4 / 11 | |
| 1.16.13 | 4 / 11 | |
| 1.16.9 | 4 / 11 | |
| 1.16.8 | 4 / 11 | |
| 1.16.7 | 4 / 11 | |
| 1.16.5 | 4 / 11 | |
| 1.16.4 | 4 / 11 | |
| 1.16.3 | 4 / 11 | |
| 1.16.2 | 4 / 11 | |
| 1.16.1 | 4 / 11 | |
| 1.16.0 | 4 / 11 | |
| 1.15.0 | 4 / 11 | |
| 1.14.0 | 4 / 11 | |
| 1.13.13 | 6 / 11 | |
| 1.13.12 | 6 / 11 | |
| 1.13.11 | 6 / 11 | |
| 1.13.10 | 6 / 11 | |
| 1.13.9 | 6 / 11 | |
| 1.13.8 | 6 / 11 | |
| 1.13.7 | 6 / 11 | |
| 1.13.6 | 6 / 11 | |
| 1.13.5 | 6 / 11 | |
| 1.13.4 | 6 / 11 | |
| 1.13.3 | 6 / 11 | |
| 1.13.2 | 6 / 11 | |
| 1.13.1 | 6 / 11 | |
| 1.13.0 | 6 / 11 | |
| 1.12.1 | 6 / 11 | |
| 1.12.0 | 6 / 11 | |
| 1.11.1 | 6 / 11 | |
| 1.11.0 | 6 / 11 | |
| 1.10.0 | 6 / 11 | |
| 1.9.0 | 6 / 11 | |
| 1.8.2 | 6 / 11 | |
| 1.8.1 | 6 / 11 | |
| 1.8.0 | 6 / 11 | |
| 1.7.3 | 6 / 11 | |
| 1.7.2 | 6 / 11 | |
| 1.7.1 | 6 / 11 | |
| 1.7.0 | 6 / 11 | |
| 1.6.25 | 6 / 11 | |
| 1.6.24 | 6 / 11 | |
| 1.6.23 | 6 / 11 | |
| 1.6.22 | 6 / 11 | |
| 1.6.21 | 6 / 11 | |
| 1.6.20 | 6 / 11 | |
| 1.6.19 | 6 / 11 | |
| 1.6.18 | 6 / 11 | |
| 1.6.17 | 6 / 11 | |
| 1.6.16 | 6 / 11 | |
| 1.6.15 | 6 / 7 | |
| 1.6.14 | 6 / 7 | |
| 1.6.13 | 6 / 7 | |
| 1.6.12 | 6 / 7 | |
| 1.6.11 | 6 / 7 | |
| 1.6.10 | 6 / 7 | |
| 1.6.9 | 6 / 7 | |
| 1.6.8 | 6 / 7 | |
| 1.6.7 | 6 / 7 | |
| 1.6.6 | 6 / 7 | |
| 1.6.5 | 6 / 7 | |
| 1.6.4 | 6 / 7 | |
| 1.6.3 | 6 / 7 | |
| 1.6.2 | 6 / 7 | |
| 1.6.1 | 6 / 7 | |
| 1.6.0 | 6 / 7 | |
| 1.5.0 | 6 / 7 | |
| 1.4.2 | 6 / 7 | |
| 1.4.1 | 6 / 7 | |
| 1.4.0 | 6 / 7 | |
| 1.3.2 | 6 / 7 | |
| 1.3.1 | 6 / 7 | |
| 1.3.0 | 6 / 7 | |
| 1.2.3 | 6 / 7 | |
| 1.2.2 | 6 / 7 | |
| 1.2.1 | 6 / 7 | |
| 1.2.0 | 6 / 7 |
v1.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.