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
- 7
- First published
- May 2026
- Publisher
- queue-it
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":["@queue-it/[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":["@queue-it/[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
buildnx build eslint-configmajorpnpm version majorminorpnpm version minorpatchpnpm version patchreleasepnpm publish --access public
Dependencies15
@eslint/js10.0.1@eslint/json2.0.0@nx/eslint-plugin22.7.5@smarttools/eslint-plugin-rxjs1.0.22@stylistic/eslint-plugin5.10.0@vitest/eslint-plugin1.6.19angular-eslint21.4.0eslint-import-resolver-typescript4.4.5eslint-plugin-boundaries6.0.2eslint-plugin-import-x4.16.2eslint-plugin-playwright2.10.4eslint-plugin-storybook10.4.2eslint-plugin-unicorn65.0.0globals17.6.0typescript-eslint8.61.0