@bpmn-io/feel-editor
Editor for FEEL expressions.
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): barinali is a listed maintainer in the bpmn-io org; the actual publisher barmac has a clean track record. | ai | |
| provenance | publisher-changed | AI (provenance): barmac is a known trusted publisher in the bpmn-io org with strong track record; transition appears legitimate. | ai | |
| dependencies | unvetted-dep:min-dom | AI (dependencies): min-dom is a well-known bpmn-io utility; stable dep for this package. | ai | |
| dependencies | unvetted-dep:@bpmn-io/feel-lint | AI (dependencies): First-party bpmn-io dep; consistent with this package's scope. | ai | |
| dependencies | unvetted-dep:@bpmn-io/lang-feel | AI (dependencies): First-party bpmn-io dep; consistent with this package's scope. | ai | |
| dependencies | unvetted-dep:@camunda/feel-builtins | AI (dependencies): First-party Camunda dep; consistent with this package's scope. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.5.2 | 12 / 32 | |
| 2.5.1 | 12 / 32 | |
| 2.5.0 | 12 / 32 | |
| 2.4.0 | 12 / 32 | |
| 2.3.0 | 11 / 32 | |
| 2.2.0 | 11 / 32 | |
| 2.1.0 | 11 / 32 | |
| 2.0.0 | 11 / 32 | |
| 1.12.1 | 11 / 33 |
v2.5.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.