PkgRadar

Package evidence

@imtbl/[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
3
First published
Jul 2024
Publisher
platform-sa

Recommended action

Looks clean — keep monitoring

No 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":["@imtbl/[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":["@imtbl/[email protected]"],"fail_on":"review"}'
Publisherplatform-sa
Artifact bytes2,170
Previous version0.0.1
Published2024-09-23T05:34:19.779Z
SHA-256d36c701f75607d7010071244ef9c7fd39d763f761f131377311524d13bba1489

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.0.2Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts13
  • buildnpm run build:ts
  • build:tstsup src/index.ts --dts
  • format:fixbiome format --write ./
  • lintnpm run typecheck && npm run lint:check
  • lint:checkbiome check ./
  • lint:check:fixbiome check --write ./
  • packnpm pack
  • prebuildrm -rf ./dist
  • publish-packageif can-npm-publish; then cd dist; npm publish --access public; else echo 'Skipping package npm publish'; fi
  • testnpm run test:jest:run
  • test:jest:ciNODE_ENV=test jest --coverage
  • test:jest:runNODE_ENV=test jest
  • typechecktsc --noEmit
Dependencies1
  • buffer^6.0.3