PkgRadar

Package evidence

warpos==0.1.2

Credential File Packaged: warpos-0.1.2/.pypirc

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
2
First published
Jun 2026

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":["warpos==0.1.2"],"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":["warpos==0.1.2"],"fail_on":"high"}'
Publisherunknown
Artifact bytes26,428
Previous versionnone
Published2026-06-05T04:59:16
SHA-2567a2a43f39c14acf89a7adf59a6b8ffc8f719c7486f03d512e13e380ff86ea0b6

Why flagged

What the scanner saw

Credential File Packaged: warpos-0.1.2/.pypirc

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

Availability ledger

available

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

Evidence

Static findings

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

SeverityKindPathDetailPoints
highCredential File Packagedwarpos-0.1.2/.pypircwarpos-0.1.2/.pypirc35