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
- 22
- First published
- May 2026
- Publisher
- fredkschott
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":["@flue/[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":["@flue/[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
Scripts4
buildtsdowncheck:typestsc --noEmittestvitest runtest:watchvitest
Dependencies16
@earendil-works/pi-agent-core^0.79.4@earendil-works/pi-ai^0.79.4@hono/node-server^2.0.3@hono/standard-validator^0.2.0@modelcontextprotocol/sdk^1.29.0@standard-community/standard-json^0.3.5@standard-community/standard-openapi^0.2.9@valibot/to-json-schema^1.3.0hono^4.8.3hono-openapi^1.3.0js-yaml^4.1.1just-bash^3.0.1openapi-types^12.1.3quansync^0.2.11ulidx^2.4.1valibot^1.1.0