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
- 10
- First published
- Apr 2026
- Publisher
- iadewunmi
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":["@lumiarq/[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":["@lumiarq/[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
Scripts7
buildtsc -p tsconfig.build.jsonlinteslint src tests --ext .tspublish:allnode scripts/publish.mjs --publishpublish:dry-runnode scripts/publish.mjstestvitest runtest:coveragevitest run --coveragetypechecktsc -p tsconfig.json --noEmit
Dependencies12
@lumiarq/agent1.1.0@lumiarq/ai1.2.0@lumiarq/context1.0.1@lumiarq/generator1.0.1@lumiarq/pack-django1.0.1@lumiarq/pack-laravel1.0.1@lumiarq/pack-lumiarq1.0.1@lumiarq/pack-nextjs1.0.1@lumiarq/planner1.0.1@lumiarq/rag0.1.0@lumiarq/tinker1.0.1@lumiarq/verifier1.0.1