@datadog/browser-logs
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 | obfuscated-file:bundle/datadog-logs.js | AI (source-diff): Standard minified browser bundle built by the package's own build script; not malicious obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New files are build artifacts (bundle + cjs/esm outputs) from the added prepack build step. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects inclusion of built bundle artifacts, consistent with the new prepack script. | ai | |
| dependencies | unvetted-dep:@datadog/browser-core | AI (dependencies): Sibling package in the same Datadog browser-sdk monorepo; always a co-versioned internal dep. | ai | |
| provenance | no-provenance | AI (provenance): Datadog browser-sdk predates provenance attestation; absence is consistent across all prior versions. | ai | |
| dependencies | unvetted-peer-dep:@datadog/browser-rum | AI (dependencies): Optional sibling peer dep in the same Datadog monorepo; stable pattern across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established Datadog SDK package; missing description is a stable metadata quirk, not a risk indicator. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 1 / 0 | |
| 7.1.0 | 1 / 0 | |
| 7.0.0 | 1 / 0 | |
| 6.33.0 | 1 / 0 | |
| 6.32.0 | 1 / 0 | |
| 6.31.0 | 1 / 0 | |
| 6.30.1 | 1 / 0 | |
| 6.29.0 | 1 / 0 | |
| 6.28.1 | 1 / 0 | |
| 6.28.0 | 1 / 0 | |
| 6.27.1 | 1 / 0 | |
| 6.27.0 | 1 / 0 | |
| 6.26.0 | 1 / 0 | |
| 6.25.4 | 1 / 0 | |
| 6.25.3 | 1 / 0 | |
| 6.25.2 | 1 / 0 | |
| 6.25.1 | 1 / 0 | |
| 6.25.0 | 1 / 0 | |
| 6.24.1 | 1 / 0 | |
| 6.24.0 | 1 / 0 | |
| 6.23.0 | 1 / 0 | |
| 6.22.0 | 1 / 0 | |
| 6.21.2 | 1 / 0 | |
| 6.21.1 | 1 / 0 | |
| 6.21.0 | 1 / 0 | |
| 6.20.0 | 1 / 0 | |
| 6.19.0 | 1 / 0 | |
| 6.18.1 | 1 / 0 | |
| 6.18.0 | 1 / 0 | |
| 6.17.0 | 1 / 0 | |
| 6.16.0 | 1 / 0 | |
| 6.14.0 | 1 / 0 | |
| 6.13.0 | 1 / 0 | |
| 6.12.3 | 1 / 0 | |
| 6.12.2 | 1 / 0 | |
| 6.12.1 | 1 / 0 | |
| 6.12.0 | 1 / 0 | |
| 6.10.1 | 1 / 0 | |
| 6.10.0 | 1 / 0 | |
| 6.9.0 | 1 / 0 | |
| 6.8.0 | 1 / 0 | |
| 6.7.0 | 1 / 0 | |
| 6.6.4 | 1 / 0 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.31.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.25.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.