@datadog/browser-rum-angular
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Datadog uses 0.0.0 as a placeholder for scoped package namespace reservation; not a malware signal for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Empty placeholder package under the official @datadog scope; sparse metadata is expected for a namespace reservation. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 2 / 6 | |
| 7.1.0 | 2 / 6 | |
| 7.0.0 | 2 / 6 | |
| 6.33.0 | 2 / 6 | |
| 6.32.0 | 2 / 5 | |
| 0.0.0 | 0 / 0 |
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.