PkgRadar

Package evidence

otoe==0.1.3

Py Runtime Subprocess: subprocess call — process spawning.

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
4
First published
May 2026
Publisher
Ale

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

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":["otoe==0.1.3"],"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":["otoe==0.1.3"],"fail_on":"review"}'
PublisherAle
Artifact bytes102,025
Previous versionnone
Published2026-05-26T19:04:59
SHA-25699313f4512c79f25e02c8cbbdb035e32000e6a734a7260864da744c2959da4ec

Why flagged

What the scanner saw

Py Runtime Subprocess: subprocess call — process spawning.

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

Availability ledger

available

review
Last checked
reviewRisk
20Score
0.1.3Version
Status history (1 event)
  1. new → available · risk review · score 20 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
mediumPy Runtime Subprocessotoe-0.1.3/src/otoe/cli.pysubprocess call — process spawning.20