@datadog/rspack-plugin
Datadog Rspack Plugin
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:outdent | AI (phantom-deps): outdent is listed as a runtime dependency in package.json; phantom-dep false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Datadog package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.1.8 | 13 / 18 | |
| 3.1.7 | 13 / 18 | |
| 3.1.6 | 13 / 18 | |
| 3.1.5 | 13 / 18 | |
| 3.1.4 | 11 / 18 | |
| 3.1.1 | 11 / 18 | |
| 3.1.0 | 11 / 18 | |
| 3.0.9 | 10 / 18 | |
| 3.0.8 | 10 / 18 | |
| 3.0.6 | 10 / 18 | |
| 3.0.4 | 10 / 18 |
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.