dmn-js-boxed-expression
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@bpmn-io/dmn-variable-resolver | AI (dependencies): First-party bpmn-io dependency, part of the same ecosystem. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal monorepo maintainer roster churn, publisher is a known long-standing maintainer. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate bpmn-io monorepo package; spam-flagged maintainers are historical org members, not indicative of malicious intent. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 17.9.0 | 7 / 4 | |
| 17.8.0 | 7 / 4 | |
| 17.7.0 | 7 / 4 | |
| 17.6.0 | 7 / 4 | |
| 17.5.0 | 7 / 4 | |
| 17.3.0 | 7 / 4 |
v17.9.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (barmac) than the most recent previously approved version (ev-camunda) on 2026-07-10, but barmac is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.