diagram-js
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine team churn in the bpmn-io org; not indicative of takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Spam flag on co-maintainers is a false positive for this well-established bpmn-io org package. | ai | |
| dependencies | unvetted-dep:min-dom | AI (dependencies): Core bpmn-io ecosystem dependency, stable across many diagram-js versions. | ai | |
| dependencies | unvetted-dep:min-dash | AI (dependencies): Core bpmn-io ecosystem dependency, stable across many diagram-js versions. | ai | |
| dependencies | unvetted-dep:tiny-svg | AI (dependencies): Core bpmn-io ecosystem dependency, stable across many diagram-js versions. | ai | |
| provenance | no-provenance | AI (provenance): Established bpmn-io package; provenance absence is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:inherits-browser | AI (dependencies): Core bpmn-io ecosystem dependency, stable across many diagram-js versions. | ai | |
| dependencies | unvetted-dep:path-intersection | AI (dependencies): Core bpmn-io ecosystem dependency, stable across many diagram-js versions. | ai | |
| dependencies | unvetted-dep:@bpmn-io/diagram-js-ui | AI (dependencies): Core bpmn-io ecosystem dependency, stable across many diagram-js versions. | ai | |
| dependencies | unvetted-dep:object-refs | AI (dependencies): Core bpmn-io ecosystem dependency, stable across many diagram-js versions. | ai | |
| dependencies | unvetted-dep:didi | AI (dependencies): Core bpmn-io ecosystem dependency, stable across many diagram-js versions. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 15.23.0 | 9 / 26 | |
| 15.22.0 | 9 / 26 | |
| 15.21.0 | 9 / 26 | |
| 15.20.1 | 9 / 26 | |
| 15.20.0 | 9 / 26 | |
| 15.19.0 | 9 / 26 | |
| 15.18.1 | 9 / 26 | |
| 15.18.0 | 9 / 27 | |
| 15.17.0 | 9 / 26 | |
| 15.16.0 | 9 / 26 | |
| 15.15.1 | 9 / 26 | |
| 15.15.0 | 9 / 26 | |
| 15.14.0 | 9 / 26 | |
| 15.13.0 | 9 / 26 | |
| 15.12.0 | 9 / 26 | |
| 15.8.0 | 9 / 26 | |
| 15.7.0 | 9 / 26 | |
| 15.6.0 | 9 / 26 | |
| 15.5.0 | 9 / 26 | |
| 15.4.0 | 9 / 27 | |
| 15.3.1 | 9 / 27 | |
| 15.3.0 | 9 / 27 | |
| 15.2.4 | 9 / 27 | |
| 15.2.3 | 9 / 27 | |
| 15.2.2 | 9 / 27 | |
| 15.2.1 | 9 / 27 | |
| 15.2.0 | 9 / 27 | |
| 15.1.0 | 9 / 27 | |
| 15.0.0 | 9 / 27 |
v15.23.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alekseymanetov) than the most recent previously approved version (nikku) on 2026-07-23, but alekseymanetov 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.
v15.22.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nikku) than the most recent previously approved version (barmac) on 2026-07-13, but nikku 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.
v15.21.0
2 findings[Accepted risk] Package 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 (nikku) 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.
v15.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.18.1
3 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Maintainer jarekdanielak is flagged as spam; stable reject signal for this package under this publisher.) Matched 1 signal(s), weighted score 3: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: barinali, jarekdanielak, bpmn-io-admin.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nikku) than the most recent previously approved version (jarekdanielak) on 2026-07-02, but nikku 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.
v15.18.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jarekdanielak) than the most recent previously approved version (nikku) on 2026-06-23, but jarekdanielak 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.
v15.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.15.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nikku) than the most recent previously approved version (jarekdanielak) on 2026-06-03, but nikku 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.
v15.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nikku) than the most recent previously approved version (barmac) on 2026-02-05, but nikku 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.
v15.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.0
2 findings[Accepted risk] Package 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 (nikku) on 2026-01-22, 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.
v15.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nikku) than the most recent previously approved version (simon-steinruecken-camunda) on 2026-01-07, but nikku 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.
v15.4.0
2 findings[Accepted risk] Package 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 (simon-steinruecken-camunda) on 2025-09-23, 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.
v15.3.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nikku) than the most recent previously approved version (simon-steinruecken-camunda) on 2025-09-19, but nikku 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.
v15.3.0
2 findingsThis version was published by a different npm account than previous versions on 2025-04-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nikku) than the most recent previously approved version (barmac) on 2024-11-21, but nikku 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.
v15.2.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nikku) than the most recent previously approved version (barmac) on 2024-11-15, but nikku 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.
v15.2.1
2 findings[Accepted risk] Package 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 (nikku) on 2024-11-14, 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.
v15.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nikku) than the most recent previously approved version (jarekdanielak) on 2024-11-04, but nikku 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.
v15.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.