All @camunda/camunda-api-zod-schemas versions

@camunda/camunda-api-zod-schemas @0.0.65

rejected
This version was rejected. It did not pass GreenFlagged's security review and is not served by the registry. The findings and risk dispositions below explain why.
25
Risk Score
LicenseRef-Camunda-1.0
License
No
Install Scripts
0
Dependencies
7
Dev Dependencies
101.6 KB
Package Size
Published

Zod schemas and TypeScript types for Camunda 8 unified API

Maintainers

nikkubarmacmaxtruphilippfrommemarstammcamunda_itomranabazidhusnauygurskaiir-camundavsgoulartyhaskellfrancesco.camundaurbanisierungjroquescamundaev-camundaztefanieemoloneymarcello.barile-camunda

Keywords

camundazod

Dev Dependencies (7)

PackageConstraintRegistry Status
zod ^4.3.6 auto_approved
vite 8.0.10 auto_approved
typescript 6.0.3 auto_approved
@types/node 25.6.0 auto_approved
changelogen 0.6.2 No greenflagged match
vite-plugin-dts 4.5.4 auto_approved
vite-plugin-circular-dependency 0.5.0 No greenflagged match

Changes from v0.0.64

No metadata changes detected.

File Changes

0 added 0 removed 3 modified size delta: +1.0 KB

Risk Dispositions (1 applicable to this version, 0 other)

Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.

Rule Source Disposition Author Reason
regressed-provenance provenance reject AI AI (provenance): Loss of CI/CD provenance combined with publisher change is a strong compromise indicator for this package.

SAST Findings (2)

HIGH Provenance attestation missing — previous versions had it provenance

This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. The axios attack (March 2026) exhibited exactly this pattern.

INFO Publisher changed: GitHub Actions → omranabazid (on 2026-05-13) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.

Review Summary

Risk score: 25. Findings: 1 high (+25), 2 info (+0).

Commit: 4b891fc307a1 Browse source

Published to npm: