PkgRadar

Package evidence

@zimbra/[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
88Mature · −50% score
First published
Mar 2018
Publisher
silentsakky

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":["@zimbra/[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":["@zimbra/[email protected]"],"fail_on":"review"}'
Publishersilentsakky
Artifact bytes511,440
Previous version12.0.1-master.1999cd1.0
Published2026-06-01T07:44:38.105Z
SHA-25670a3cab6205b0ff6b27d33bf6907445f7bc6ca42b0bd4f6353774ebcf861dace

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
12.0.1-master.89714d0.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

Scripts3
  • buildnpm run generateIconVariablesFile
  • generateIconVariablesFilenode generate-icon-variables.js
  • prepublishOnlyif [ "$CI" != "true" ]; then npm run build && git commit -am $npm_package_version && git tag $npm_package_version && git push && git push --tags; fi