@amplitude/plugin-custom-enrichment-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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Migration from sdk.dev to GitHub Actions CI; SLSA provenance confirms legitimate CI publish. | ai | |
| source-diff | obfuscated-file:lib/scripts/amplitude-min.js | AI (source-diff): Rollup+Terser minified bundle; standard build output for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Core feature of this plugin: deserializing user-supplied function bodies via new Function(). Stable and intentional across versions. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.1.10 | 2 / 7 | |
| 0.1.9 | 2 / 7 | |
| 0.1.8 | 2 / 7 | |
| 0.1.7 | 2 / 7 | |
| 0.1.6 | 2 / 7 | |
| 0.1.5 | 2 / 7 | |
| 0.1.4 | 2 / 7 | |
| 0.1.3 | 2 / 7 | |
| 0.1.2 | 2 / 7 | |
| 0.1.1 | 2 / 7 | |
| 0.1.0 | 2 / 7 | |
| 0.0.1 | 2 / 7 |
v0.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
3 findingsThis version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
3 findingsThis version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
3 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.