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
- 112
- First published
- Jan 2026
- Publisher
- joaohcrangel
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":["@hed-hog/[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":["@hed-hog/[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
Scripts5
buildtsc --project tsconfig.production.jsonlinteslint "{src,apps,libs,test}/**/*.ts"patchnpx ts-node ../../scripts/patch.ts libraries/tagprebuildpnpm --dir ../.. exec ts-node ./scripts/build-dependencies.ts libraries/tagprodpnpm run patch && pnpm run build && pnpm publish --access public --no-git-checks
Dependencies10
@hed-hog/api0.0.8@hed-hog/api-locale0.0.14@hed-hog/api-pagination0.0.7@hed-hog/api-prisma0.0.6@hed-hog/core0.0.358@nestjs/common*@nestjs/config^4.0.2@nestjs/core^11@nestjs/jwt^11@nestjs/mapped-types*