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
- 169
- Versions published
- 4
- First published
- May 2026
- Publisher
- danii1
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":["@getdevintern/[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":["@getdevintern/[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
Scripts13
buildbun run build.tscleanrm -rf distdevbun run src/index.tsformatoxfmt "src/**/*.ts" "tests/**/*.ts" "build.ts"format:checkoxfmt --check "src/**/*.ts" "tests/**/*.ts" "build.ts"install-globalbun run build && bun linklintoxlint .preparebun run buildprepublishOnlybun run clean && bun run build && bun run typecheckstartbun run src/index.tstestbun testtypecheckbun run tsc --noEmituninstall-globalbun unlink
Dependencies5
@types/turndown^5.0.5commander^11.0.0dotenv^16.3.1p-queue^9.0.1turndown^7.2.0