@bpmn-io/element-templates-validator
Validate element templates based on JSON Schema
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@camunda/zeebe-configuration-templates-json-schema | AI (dependencies): Official Camunda schema companion package, consistent with existing deps. | ai | |
| phantom-deps | phantom-dep:@camunda/zeebe-configuration-templates-json-schema | AI (phantom-deps): Config-referenced schema data, same pattern as other accepted phantom deps. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Flagged names are unrelated past maintainers, not current publisher nikku. | ai | |
| 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 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.25.0 | 5 / 13 | |
| 2.24.0 | 5 / 13 | |
| 2.23.0 | 4 / 13 | |
| 2.22.0 | 4 / 13 | |
| 2.21.0 | 4 / 13 | |
| 2.20.2 | 4 / 13 | |
| 2.16.0 | 4 / 13 | |
| 2.14.0 | 4 / 13 | |
| 2.4.0 | 4 / 13 | |
| 2.3.3 | 4 / 13 | |
| 2.3.2 | 4 / 13 | |
| 2.3.1 | 4 / 13 | |
| 2.3.0 | 4 / 13 | |
| 2.2.0 | 4 / 13 | |
| 2.1.0 | 4 / 13 | |
| 2.0.1 | 4 / 13 | |
| 2.0.0 | 4 / 13 |
v2.25.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (barmac) than the most recent previously approved version (nikku) on 2026-07-24, but barmac 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.24.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nikku) than the most recent previously approved version (alekseymanetov) on 2026-07-16, but nikku 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.23.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nikku) than the most recent previously approved version (jarekdanielak) on 2026-06-25, but nikku 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.20.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alekseymanetov) than the most recent previously approved version (nikku) on 2026-06-29, but alekseymanetov 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.3.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (barmac) than the most recent previously approved version (philippfromme) on 2025-01-28, but barmac 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.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (philippfromme) than the most recent previously approved version (nikku) on 2025-01-23, but philippfromme 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.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (barmac) than the most recent previously approved version (nikku) on 2025-01-16, but barmac 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.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1
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.