@segment/analytics-browser-actions-contentstack-web
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Auto-generated @segment monorepo sub-package; missing metadata is a known pattern across all 253 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @segment monorepo sub-package pattern; not indicative of malice. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.41.0 | 1 / 0 | |
| 1.40.0 | 1 / 0 | |
| 1.39.0 | 1 / 0 | |
| 1.38.0 | 1 / 0 | |
| 1.37.0 | 1 / 0 | |
| 1.36.0 | 1 / 0 | |
| 1.35.0 | 1 / 0 | |
| 1.34.0 | 1 / 0 | |
| 1.33.0 | 1 / 0 | |
| 1.32.0 | 1 / 0 | |
| 1.31.0 | 1 / 0 | |
| 1.30.0 | 1 / 0 | |
| 1.29.0 | 1 / 0 | |
| 1.28.0 | 1 / 0 | |
| 1.27.0 | 1 / 0 | |
| 1.26.0 | 1 / 0 | |
| 1.25.0 | 1 / 0 |
v1.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.