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
- 13
- Versions published
- 28
- First published
- Jan 2026
- Publisher
- 7365admin1
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":["@7365admin1/[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":["@7365admin1/[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
Scripts3
buildtsup src/index.ts --format cjs,esm --dtslinttscreleaseyarn run build && changeset publish
Dependencies21
@7365admin1/core^2.45.0@7365admin1/node-server-utils^1.4.0@types/qrcode^1.5.6@types/urllib^2.33.0cors^2.8.5dotenv^16.4.7express^4.21.2fast-levenshtein^3.0.0joi^17.13.3jsonwebtoken^9.0.2moment-timezone^0.6.0mongodb^6.18.0multer^1.4.5-lts.2node-cron^3.0.3puppeteer^24.33.1qrcode^1.5.4redis^4.6.10urllib^4.8.2uuid^11.1.0xlsx^0.18.5zod^3.24.2