@segment/analytics-signals
See the [official auto-instrumentation documentation](https://segment.com/docs/connections/auto-instrumentation/web-setup/).
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/umd/analytics-signals.global.js | AI (source-diff): Standard webpack UMD minified bundle; sample shows readable JS, not obfuscated payload. | ai | |
| source-diff | encoded-string-file:dist/umd/analytics-signals.umd.js | AI (source-diff): Standard webpack UMD minified bundle; sample shows readable JS, not obfuscated payload. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped Segment/Twilio SDK; sparse metadata is typical for corporate monorepo packages, not spam. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.4.4 | 5 / 9 | |
| 2.4.2 | 5 / 9 | |
| 2.4.1 | 5 / 9 | |
| 2.4.0 | 5 / 9 | |
| 2.3.0 | 5 / 9 | |
| 2.2.1 | 5 / 9 | |
| 2.2.0 | 5 / 9 | |
| 2.1.0 | 5 / 9 | |
| 2.0.1 | 5 / 9 | |
| 2.0.0 | 4 / 9 |
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.