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
- 62
- First published
- May 2026
- Publisher
- suleimansh
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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":["@pilotiq/[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":["@pilotiq/[email protected]"],"fail_on":"review"}'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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts7
buildtsc -p tsconfig.build.json && pnpm run copy-assetscleanrm -rf distcopy-assetsmkdir -p dist/styles && cp -R src/styles/*.css dist/styles/devtsc -p tsconfig.build.json --watch & pnpm run copy-assets; waitlinteslint srctesttsc -p tsconfig.test.json && node --test "dist-test/**/*.test.js"; EXIT=$?; rm -rf dist-test; exit $EXITtypechecktsc --noEmit
Dependencies8
@dnd-kit/core^6.3.1@dnd-kit/modifiers^9.0.0@dnd-kit/sortable^10.0.0@dnd-kit/utilities^3.2.2jiti^2.6.0marked^14react-image-crop^11.0.10sanitize-html^2.17.3