@dfns/dfns-key-import-bundler No license 2 versions

@dfns/dfns-key-import-bundler

npm Repository Homepage

Versions

—

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

asaraprrbgntdfns-github-botthibault2ssdfns_nikdrunkirishcoderarnaud-dfnsncornwelladriendfnstlm-dfnsdenis-dfnsueiuzbrcnmlmqaharrisontross-dfnstgtyluisalmeida-dfnsmarkdfnsjonas-dfnsromasychevski-dfnsmbj-dfns

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:api-obfuscation-reflect	AI (semgrep): Standard wasm-bindgen glue code pattern; Reflect.get() is generated boilerplate, not obfuscation.	ai	2026/04/29
semgrep	semgrep:new-function-constructor	AI (semgrep): new Function() in wasm-bindgen output is standard generated glue for WASM string interop, not dynamic code execution.	ai	2026/04/29

Versions (showing 2 of 2)

Version	Deps	Published
0.4.0	0 / 0	2025-11-03
0.3.0	0 / 0	2025-10-06

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.