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
- 6
- Versions published
- 7
- First published
- Apr 2026
- Publisher
- geequlim
Recommended action
Looks clean — keep monitoringNo 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":["@tinyaxis/[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":["@tinyaxis/[email protected]"],"fail_on":"review"}'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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Dependencies35
@sinclair/typebox^0.34.49async-lock^1.4.1axios^1.15.0chalk^5.6.2cli-highlight^2.1.11commander^14.0.3cross-env^10.1.0dotenv^17.3.1esm-hook^0.1.4expr-eval^2.0.2fast-glob^3.3.3fecha^4.2.3file-type^21.3.2filesize^11.0.15glob^13.0.6http-status-codes^2.3.0js-md5^0.8.3js-yaml^4.1.1json-stable-stringify^1.3.0lookpath^1.2.3memory-cache^0.2.0merge-anything^6.0.6mime-types^3.0.2mkcert^3.2.0msgpackr^1.11.9parse-duration^2.1.5pino^10.3.1qs^6.15.1shorthash2^1.0.5snappyjs^0.7.0- …and 5 more.