PkgRadar

Package evidence

@fitskill/[email protected]

no findings

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":["@fitskill/[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":["@fitskill/[email protected]"],"fail_on":"review"}'
Publisherhao65103940
Artifact bytes8,131
Previous version0.3.2
Published2026-05-19T05:59:34.139Z
SHA-25619fb9820d1a7cc9b6845d5734352673e4fcdcff111e067a4468159cf9cf3ae07

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.3.3Version
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

Scripts1
  • startnode bin/f2chub.js
Dependencies5
  • chalk^5.3.0
  • commander^12.1.0
  • extract-zip^2.0.1
  • ora^8.0.1
  • yaml^2.9.0