@camunda/example-data-properties-provider
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 |
|---|---|---|---|---|
| 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 |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 2 / 29 | |
| 1.4.0 | 2 / 29 | |
| 1.3.0 | 2 / 28 | |
| 1.2.1 | 2 / 28 | |
| 1.2.0 | 2 / 25 | |
| 1.1.1 | 2 / 25 | |
| 1.1.0 | 2 / 25 | |
| 1.0.1 | 1 / 25 | |
| 1.0.0 | 1 / 25 |
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.