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
- 3
- First published
- May 2026
- Publisher
- aparna_dev
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":["@loan-risk/[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":["@loan-risk/[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
Scripts 4
Sign in to view install / lifecycle script contents.
Dependencies20
@loan-risk/core1.0.5@loan-risk/logger1.0.5@opentelemetry/api^1.9.1@opentelemetry/auto-instrumentations-node^0.76.0@opentelemetry/exporter-trace-otlp-http^0.218.0@opentelemetry/sdk-node^0.218.0compression^1.8.1cors^2.8.5dotenv^17.2.3express^5.1.0express-rate-limit^8.5.2helmet^8.1.0pino^10.3.1pino-http^11.0.0prom-client^15.1.3redis^6.0.0swagger-jsdoc^6.2.8swagger-ui-express^5.0.1uuid^14.0.0zod^4.4.3