@camunda/zeebe-element-templates-json-schema

Package 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.

Package 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 (barmac) 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.

Package 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 (alekseymanetov) on 2026-07-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.

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: barinali, jarekdanielak. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

Package 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-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.

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: barinali, jarekdanielak. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: barinali, jarekdanielak. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: barinali, jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

Package 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 (barmac) on 2025-08-19, 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.

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

Package 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 (barmac) on 2025-08-18, 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.

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

This version was published by a different npm account than previous versions on 2025-05-08. This could indicate a legitimate maintainer transition or an account compromise.

[Reject — re-review on republish] (prior reject: AI (bogus-package): SPAM-FLAGGED publisher jarekdanielak; generalizes to any version published by this actor.) Matched 2 signal(s), weighted score 4: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: jarekdanielak, simon-steinruecken-camunda. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared.

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

Package 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.

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

Package 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.

Package 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.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

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

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

This version was published by a different npm account (marstamm) than the most recent previously approved version (barmac) on 2024-02-07, but marstamm 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.

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

Package 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 (marstamm) on 2023-12-13, 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.

Package 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 (marstamm) on 2023-11-27, 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.

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

This version was published by a different npm account (marstamm) than the most recent previously approved version (barmac) on 2023-11-22, but marstamm 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.

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

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

Package 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 (marstamm) on 2023-10-10, 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.

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

This version was published by a different npm account (beatrizmendes) than the most recent previously approved version (marstamm) on 2023-08-25, but beatrizmendes 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.

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

This version was published by a different npm account (marstamm) than the most recent previously approved version (barmac) on 2023-08-23, but marstamm 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.

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

This version was published by a different npm account (beatrizmendes) than the most recent previously approved version (barmac) on 2023-08-03, but beatrizmendes 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.

Package 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 (beatrizmendes) on 2023-04-25, 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.

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

This version was published by a different npm account (beatrizmendes) than the most recent previously approved version (marstamm) on 2023-03-02, but beatrizmendes 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.

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

This version was published by a different npm account (marstamm) than the most recent previously approved version (nikku) on 2023-02-03, but marstamm 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.

Package 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 (marstamm) on 2022-08-23, 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.

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: beatrizmendes.

This version was published by a different npm account (beatrizmendes) than the most recent previously approved version (marstamm) on 2022-07-04. It has since remained available on npm for 1482 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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

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

This version was published by a different npm account (marstamm) than the most recent previously approved version (pinussilvestrus) on 2022-04-01, but marstamm 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.

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

This version was published by a different npm account (pinussilvestrus) than the most recent previously approved version (marstamm) on 2022-03-31, but pinussilvestrus 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.

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

This version was published by a different npm account (marstamm) than the most recent previously approved version (pinussilvestrus) on 2022-03-17. It has since remained available on npm for 1591 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

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

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.