diagram-js-direct-editing
Direct editing support for 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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Long-established bpmn-io package; spam-publisher signal reflects org-level maintainer rotation, not actual spam. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy consistent with stable mature package; no code changes indicate routine maintenance release. | ai | |
| dependencies | unvetted-dep:min-dom | AI (dependencies): min-dom is a bpmn-io utility; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:min-dash | AI (dependencies): min-dash is a bpmn-io utility; stable dependency for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.5.1 | 2 / 16 | |
| 3.5.0 | 2 / 16 | |
| 3.4.0 | 2 / 16 | |
| 3.3.0 | 2 / 16 | |
| 3.2.0 | 2 / 17 | |
| 3.1.0 | 2 / 17 | |
| 3.0.1 | 2 / 17 | |
| 3.0.0 | 2 / 17 |
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.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 (jarekdanielak) than the most recent previously approved version (nikku) on 2024-11-06, 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.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.