← Home

dmn-js-shared

npm Repository Homepage
8
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-camundavsgoulartbarinalijarekdanielakev-camundaalekseymanetov

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Established bpmn-io ecosystem package; sparse README and no keywords are cosmetic, not spam indicators. ai
dependencies unvetted-dep:inferno AI (dependencies): inferno is a well-known UI library; stable dep for this package. ai
dependencies unvetted-dep:table-js AI (dependencies): table-js is a bpmn-io org package; expected dep for dmn-js-shared. ai
dependencies unvetted-dep:dmn-moddle AI (dependencies): dmn-moddle is a bpmn-io org package; expected dep for dmn-js-shared. ai
dependencies unvetted-dep:selection-ranges AI (dependencies): selection-ranges is a known utility; stable dep for this package. ai
dependencies unvetted-dep:selection-update AI (dependencies): selection-update is a known utility; stable dep for this package. ai

Versions (showing 8 of 8)

Version Deps Published
17.8.1 11 / 2
17.8.0 11 / 2
17.7.0 11 / 2
17.6.0 11 / 2
17.5.0 11 / 2
17.4.0 11 / 2
17.3.0 11 / 2
17.2.1 11 / 2

v17.8.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: ev-camunda → barmac (on 2026-05-06, known maintainer) provenance

This version was published by a different npm account (barmac) than the most recent previously approved version (ev-camunda) on 2026-05-06, 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.8.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.

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

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

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

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

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

v17.2.1

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.