@datadog/browser-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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): Internal monorepo sub-package; missing README/keywords/deps is expected for @datadog/browser-core. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established Datadog SDK sub-package; no description is a stable pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Long-standing Datadog package predating provenance attestation; no provenance is consistent across all 321 versions. | ai |
Versions (showing 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 7.6.1 | 1 / 1 | |
| 7.6.0 | 1 / 1 | |
| 7.5.0 | 1 / 2 | |
| 7.4.0 | 1 / 2 | |
| 7.3.0 | 1 / 2 | |
| 7.2.0 | 0 / 2 | |
| 7.1.0 | 0 / 2 | |
| 7.0.0 | 0 / 2 | |
| 6.33.0 | 0 / 2 | |
| 6.32.0 | 0 / 2 | |
| 6.31.0 | 0 / 2 | |
| 6.30.1 | 0 / 2 | |
| 6.29.0 | 0 / 2 | |
| 6.28.1 | 0 / 2 | |
| 6.28.0 | 0 / 2 | |
| 6.27.1 | 0 / 2 | |
| 6.27.0 | 0 / 2 | |
| 6.26.0 | 0 / 2 | |
| 6.25.4 | 0 / 2 | |
| 6.25.3 | 0 / 2 | |
| 6.25.2 | 0 / 2 | |
| 6.25.1 | 0 / 2 | |
| 6.25.0 | 0 / 2 | |
| 6.24.1 | 0 / 2 | |
| 6.24.0 | 0 / 2 | |
| 6.23.0 | 0 / 2 | |
| 6.22.0 | 0 / 2 | |
| 6.21.2 | 0 / 0 | |
| 6.21.1 | 0 / 0 | |
| 6.21.0 | 0 / 0 | |
| 6.20.0 | 0 / 0 | |
| 6.19.0 | 0 / 0 | |
| 6.18.1 | 0 / 0 | |
| 6.18.0 | 0 / 0 | |
| 6.17.0 | 0 / 0 | |
| 6.16.0 | 0 / 0 | |
| 6.14.0 | 0 / 0 | |
| 6.13.0 | 0 / 0 | |
| 6.12.3 | 0 / 0 | |
| 6.12.2 | 0 / 0 | |
| 6.12.1 | 0 / 0 | |
| 6.12.0 | 0 / 0 | |
| 6.10.1 | 0 / 0 | |
| 6.10.0 | 0 / 0 | |
| 6.9.0 | 0 / 0 | |
| 6.8.0 | 0 / 0 | |
| 6.7.0 | 0 / 0 | |
| 6.6.4 | 0 / 0 | |
| 6.6.3 | 0 / 0 | |
| 6.6.2 | 0 / 0 | |
| 6.6.1 | 0 / 0 | |
| 6.6.0 | 0 / 0 | |
| 6.5.1 | 0 / 0 | |
| 6.5.0 | 0 / 0 | |
| 6.4.0 | 0 / 0 | |
| 6.3.0 | 0 / 0 | |
| 6.2.1 | 0 / 0 | |
| 6.2.0 | 0 / 0 | |
| 6.1.0 | 0 / 0 | |
| 6.0.0 | 0 / 0 |
v7.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.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.0.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.