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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established bpmn-io package; provenance absence is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:didi | AI (dependencies): Core bpmn-io ecosystem dependency, stable across many diagram-js versions. | 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 | |
| dependencies | unvetted-dep:object-refs | AI (dependencies): Core bpmn-io ecosystem dependency, stable across many diagram-js versions. | 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 |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 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 |
v15.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.12.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.
v15.8.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.
v15.7.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.
v15.6.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.
v15.5.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.
v15.4.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.
v15.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.