← Home

@bpmn-io/element-templates-validator

npm Repository Homepage

Validate element templates based on JSON Schema

5
Versions
MIT
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

bpmn-io-adminnikkubarmacphilippfrommemaxtruskaiir-camundavsgoulartbarinalijarekdanielakev-camundaalekseymanetov

Keywords

json-schemajson-schema-validatorelement templatesvalidatorvalidation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:json-source-map AI (phantom-deps): json-source-map is a legitimate runtime dep; phantom-dep heuristic likely misses indirect import patterns in this bundled package. ai
phantom-deps phantom-dep:@camunda/element-templates-json-schema AI (phantom-deps): Schema dep used at build/bundle time; phantom-dep heuristic fires on config-file references, not a real missing import. ai
phantom-deps phantom-dep:@camunda/zeebe-element-templates-json-schema AI (phantom-deps): Same as above — schema dep used at build time, stable false positive for this package. ai

Versions (showing 5 of 5)

Version Deps Published
2.22.0 4 / 13
2.21.0 4 / 13
2.16.0 4 / 13
2.14.0 4 / 13
2.4.0 4 / 13

v2.22.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: alekseymanetov → jarekdanielak (on 2026-05-26, known maintainer) provenance

This version was published by a different npm account (jarekdanielak) than the most recent previously approved version (alekseymanetov) on 2026-05-26, but jarekdanielak 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.

v2.16.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.14.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.

v2.4.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.