dmn-js-shared
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
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): 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 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 17.10.0 | 11 / 2 | |
| 17.9.0 | 11 / 2 | |
| 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 | |
| 17.1.0 | 11 / 2 | |
| 17.0.1 | 11 / 2 | |
| 17.0.0 | 11 / 2 |
v17.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.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 (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 findingsPackage 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-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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.