PkgRadar

Package evidence

@camunda/[email protected]

no findings

Trust signals

Why this verdict

PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.

Versions published
54Mature · −50% score
First published
Feb 2022
Publisher
alekseymanetov

Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
Block this release in CIcurl · GitHub Actions

Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.

curl -fsS https://pkgradar.com/gate/npm \
  -H "Authorization: Bearer $PKGRADAR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"specs":["@camunda/[email protected]"],"fail_on":"review"}'

GitHub Actions step:

- name: PkgRadar gate
  run: |
    curl -fsS https://pkgradar.com/gate/npm \
      -H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
      -H "Content-Type: application/json" \
      -d '{"specs":["@camunda/[email protected]"],"fail_on":"review"}'
Publisheralekseymanetov
Artifact bytes14,629
Previous version0.39.2
Published2026-04-21T14:24:09.001Z
SHA-256b9760c2bea2e37b7e99c7269fefb70bb1e3e0fc9d4c18b7e4426e1e21a66b952

Why flagged

What the scanner saw

No high-signal static finding in the saved report.

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

low
Last checked
lowRisk
0Score
0.40.0Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts8
  • allrun-s build test
  • buildrun-s build:error-messages build:schema
  • build:error-messagesnode ../../tasks/generate-error-messages.js --input=./src/error-messages.json --output=./resources/error-messages.json
  • build:schemanode ../../tasks/generate-schema.js --input=./src/schema.json --output=./resources/schema.json
  • devnpm run test -- --watch
  • preparerun-s build
  • testmocha --reporter=spec --recursive test/spec
  • test:integrationmocha --reporter=spec --recursive test/integration