PkgRadar

Package evidence

@ploomescrm/[email protected]

New Account With Lifecycle Hook: package first published 0 day(s) ago, 4 total version(s), has lifecycle hook

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
4
First published
Jun 2026
Publisher
GitHub ActionsTrusted automation · −70% score

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

Recommended action

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

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":["@ploomescrm/[email protected]"],"fail_on":"high"}'

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":["@ploomescrm/[email protected]"],"fail_on":"high"}'
Artifact bytes137,406
Previous version1.1.1
Published2026-06-17T18:51:12.392Z
SHA-256f31e8b0d461d215011b92e8a8387740e9c92ac333df484ba0b31248b3e566064

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.2.0 vs 1.1.1: "node scripts/setup.mjs"

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

Availability ledger

available

high
Last checked
highRisk
45Score
1.2.0Version
Status history (1 event)
  1. newavailable · risk high · score 45 · status changed

Evidence

Static findings

2 static · 1 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.2.0 vs 1.1.1: "node scripts/setup.mjs"40
highNew Account With Lifecycle Hookpackage.jsonpackage first published 0 day(s) ago, 4 total version(s), has lifecycle hook25
Show all 3 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.2.0 vs 1.1.1: "node scripts/setup.mjs"40
highNew Account With Lifecycle Hookpackage.jsonpackage first published 0 day(s) ago, 4 total version(s), has lifecycle hook25
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node scripts/setup.mjs"5

Manifest

Package metadata

Scripts8
  • buildtsdown
  • devtsdown --watch
  • linteslint src --max-warnings 0
  • postinstallnode scripts/setup.mjs
  • testvitest run
  • test:coveragevitest run --coverage
  • test:watchvitest
  • type-checktsc --noEmit
Dependencies8
  • @monaco-editor/react^4.7.0
  • class-variance-authority^0.7.1
  • clsx^2.1.1
  • dompurify^3.4.10
  • lucide-react^1.17.0
  • react-grid-layout^2.2.3
  • squire-rte^2.4.8
  • tailwind-merge^3.6.0