← Home

dmn-js-drd

npm Repository Homepage
14
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

bpmn-io-adminnikkubarmacphilippfrommemaxtruskaiir-camundavsgoulartbarinaliev-camundajarekdanielakalekseymanetov

Keywords

dmndmn-jsdmn-js-viewdrd

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Legitimate org maintainer rotation on established bpmn-io package; publisher has clean track record. ai
bogus-package bogus-package AI (bogus-package): Legitimate bpmn-io monorepo sub-package; flagged maintainers are known bpmn-io org members, not spam actors. ai
dependencies unvetted-dep:dmn-js-shared AI (dependencies): dmn-js-shared is a sibling package in the same bpmn-io/dmn-js monorepo; not an external risk. ai

Versions (showing 14 of 14)

Version Deps Published
17.10.0 9 / 2
17.9.0 9 / 2
17.8.1 9 / 2
17.8.0 9 / 2
17.7.0 9 / 2
17.6.0 8 / 2
17.5.0 8 / 2
17.4.0 8 / 2
17.3.0 8 / 2
17.2.1 8 / 2
17.2.0 8 / 2
17.1.0 8 / 2
17.0.1 8 / 2
17.0.0 8 / 2

v17.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.2.0

2 findings
HIGH Publisher changed: philippfromme → buckwich (on 2025-03-12) provenance

This version was published by a different npm account than previous versions on 2025-03-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v17.1.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: nikku → philippfromme (on 2025-01-24, known maintainer) provenance

This version was published by a different npm account (philippfromme) than the most recent previously approved version (nikku) on 2025-01-24, but philippfromme 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.

v17.0.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: nikku → barmac (on 2024-11-08, known maintainer) provenance

This version was published by a different npm account (barmac) than the most recent previously approved version (nikku) on 2024-11-08, 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.

v17.0.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.