@datadog/wasm-js-rewriter
Datadog instrumentation addon for Node.js
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Datadog org migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate automated release pipeline. | ai | |
| dependencies | unvetted-dep:node-gyp-build | AI (dependencies): node-gyp-build is the standard native addon binary loader; expected for this package type. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get in wasm-pack-generated JS glue code; standard WASM host binding pattern. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes inline source map comments — standard source-map parsing, not payload hiding. | ai | |
| phantom-deps | phantom-dep:node-gyp-build | AI (phantom-deps): node-gyp-build is referenced in config/build files for native addon loading; stable false positive. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function in wasm-pack glue for WASM host bindings; expected pattern for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Require uses a literal template string path to a bundled snippet file; not truly dynamic. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 5.0.2 | 4 / 31 | |
| 5.0.1 | 4 / 31 | |
| 5.0.0 | 4 / 31 | |
| 4.0.1 | 4 / 32 |
v5.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.1
2 findingsThis version was published by a different npm account than previous versions on 2025-11-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.