@bpmn-io/extract-process-variables
A util for bpmn-js to extract Camunda BPM process variables from a BPMN 2.0 diagram.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): nikku is an established bpmn-io org maintainer with 15 approved packages; transition from barmac is a legitimate org handoff. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Spam signal is from unrelated co-maintainers in the org; core package and publisher are legitimate bpmn-io project. | ai | |
| provenance | no-provenance | AI (provenance): Established bpmn-io/Camunda package; lack of provenance is common and not a risk indicator here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 1 / 13 | |
| 2.2.0 | 1 / 13 | |
| 2.1.1 | 1 / 13 | |
| 2.1.0 | 1 / 13 | |
| 2.0.0 | 1 / 13 |
v2.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. 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.
v2.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-23. 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.
v2.1.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.
v2.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.