bpmn-js-properties-panel
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/bpmn-js-properties-panel.umd.js | AI (source-diff): Flagged strings are CodeMirror BiDi lookup tables (LowTypes/ArabicTypes), a stable false positive for this bundled UMD output. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate bpmn-io project; spam-flagged co-maintainers are incidental, not indicative of malicious content. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.58.0 | 5 / 48 | |
| 5.57.0 | 5 / 48 | |
| 5.56.0 | 5 / 48 | |
| 5.55.0 | 5 / 48 | |
| 5.54.0 | 5 / 49 | |
| 5.35.0 | 5 / 49 |
v5.58.0
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
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-05-22, 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.
v5.57.0
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
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 (barmac) on 2026-05-22, 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.
v5.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.