@camunda/example-data-properties-provider
3
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
nikkubarmacmaxtruphilippfrommebarinalijarekdanielakev-camundaalekseymanetov
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 a well-established Camunda ecosystem publisher; transition from alekseymanetov is consistent with internal team changes. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal example package under @camunda scope; missing metadata is expected for org-internal tooling, not spam. | ai | |
| phantom-deps | phantom-dep:min-dash | AI (phantom-deps): min-dash is a legitimate bpmn-io utility; phantom-dep fires because it's used indirectly via bundled lib output. | ai |
v1.5.0
2 findings
HIGH
Publisher changed: alekseymanetov → nikku (on 2026-05-21)
provenance
This version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.