PkgRadar

Package evidence

@itcase/[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.

Weekly downloads
483
Versions published
28Mature · −50% score
First published
Jan 2025
Publisher
arkadiy_zamaraev

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":["@itcase/[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":["@itcase/[email protected]"],"fail_on":"review"}'
Publisherarkadiy_zamaraev
Artifact bytes3,155
Previous version1.1.50
Published2026-06-15T06:44:45.330Z
SHA-256247fcd49f39f9a173b19c4c9288fb9b7aee77f48d521d14c89218a8c4e0ebb39

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
1.1.59Version
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

Scripts6
  • buildnpm run build-css && npm run build-js
  • build-csspostcss 'src/styles/main.css' --base src --dir dist/css/ --env production
  • build-jsNODE_ENV=production rollup -c
  • devnpm run dev-css
  • dev-csspostcss 'src/styles/main.css' --base src --dir dist/css/ --env production
  • dev-jsrollup -c -w