min-dash
1
Versions
—
License
No
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
bpmn-io-adminnikkubarmacphilippfrommemaxtruskaiir-camundavsgoulartjarekdanielaksimon-steinruecken-camunda
Keywords
lodashutilitytoolbelt
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:http://bpmn.io | AI (email-domain): bpmn.io is the legitimate org; the 'email' field is actually a URL in the author string, not a real email domain. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 0 / 17 |
v5.0.0
2 findings
HIGH
Unclaimed maintainer email domain: http://bpmn.io
email-domain
Maintainer email 'http://bpmn.io' uses domain 'http://bpmn.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
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.