← Home

@camunda/ccma-saas-frontend

npm Repository Homepage

Camunda Composite Components

12
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

nikkubarmacmaxtruphilippfrommemarstammcamunda_itomranabazidhusnauygurskaiir-camundavsgoulartyhaskellfrancesco.camundaurbanisierungjroquescamundaev-camundaztefanieemoloneymarcello.barile-camunda

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Camunda org package published via GitHub Actions; missing gitHead likely reflects a CI config change, not a compromise. ai
phantom-deps phantom-dep:cron-parser AI (phantom-deps): Config-file reference in monorepo build; stable pattern for this package. ai
phantom-deps phantom-dep:mobx-react-lite AI (phantom-deps): Config-file reference in monorepo build; stable pattern for this package. ai
phantom-deps phantom-dep:mobx-state-tree AI (phantom-deps): Config-file reference in monorepo build; stable pattern for this package. ai
phantom-deps phantom-dep:@camunda/ccma-shared-types AI (phantom-deps): Same-org scoped package in monorepo; stable pattern for this package. ai
phantom-deps phantom-dep:@pactsafe/pactsafe-react-sdk AI (phantom-deps): Config-file reference in monorepo build; stable pattern for this package. ai
phantom-deps phantom-dep:@camunda/ccma-api AI (phantom-deps): Same-org scoped package in monorepo; stable pattern for this package. ai
phantom-deps phantom-dep:mobx AI (phantom-deps): mobx is a direct runtime dependency in package.json; phantom-dep is a false positive here. ai
phantom-deps phantom-dep:semver AI (phantom-deps): semver is a direct runtime dependency in package.json; phantom-dep is a false positive here. ai

Versions (showing 12 of 12)

Version Deps Published
0.0.43 8 / 31
0.0.41 8 / 28
0.0.40 8 / 28
0.0.39 8 / 28
0.0.38 8 / 28
0.0.37 8 / 28
0.0.36 8 / 28
0.0.35 8 / 28
0.0.34 8 / 28
0.0.33 8 / 28
0.0.32 8 / 28
0.0.31 8 / 28

v0.0.43

1 finding
LOW No provenance attestation provenance

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

v0.0.41

1 finding
LOW No provenance attestation provenance

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

v0.0.39

2 findings
HIGH Missing gitHead — previous versions had it provenance

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

LOW No provenance attestation provenance

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

v0.0.38

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.

v0.0.37

2 findings
HIGH Missing gitHead — previous versions had it provenance

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

LOW No provenance attestation provenance

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

v0.0.36

2 findings
HIGH Missing gitHead — previous versions had it provenance

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

LOW No provenance attestation provenance

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

v0.0.35

2 findings
HIGH Missing gitHead — previous versions had it provenance

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

LOW No provenance attestation provenance

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

v0.0.34

2 findings
HIGH Missing gitHead — previous versions had it provenance

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

LOW No provenance attestation provenance

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

v0.0.33

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.

v0.0.32

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.

v0.0.31

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.