@datadog/browser-rum-nuxt
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 org uses 0.0.0 as a placeholder/namespace reservation; not indicative of malice. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Empty placeholder release by established Datadog org; low-value signals are expected for namespace reservations. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package from Datadog; missing description is cosmetic and consistent across their SDK packages. | ai | |
| provenance | no-provenance | AI (provenance): Datadog browser-sdk packages historically lack Sigstore provenance; not a risk indicator for this publisher. | ai |
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 finding[Accepted risk] Package 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.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.