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
- Jul 2025
- Publisher
- silkalns
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":["[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":["[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
Scripts17
buildnpm run clean && cross-env webpackbuild:analyzenpm run clean && cross-env ANALYZE=true NODE_ENV=production webpackcleanshx rm -rf ./distdevwebpack-dashboard -t 'Project' -- webpack serverlintnpm run lint:js && npm run lint:scsslint:jseslint ./src ./webpack ./*.js -f table --ext .js --ext .jsxlint:scssstylelint ./src/**/*.scsspostpublishecho 'Package published successfully! View at: https://www.npmjs.com/package/adminator-admin-dashboard'prepublishOnlynpm run lint && npm run buildpreviewcross-env webpack serverrelease:minifiednpm run clean && NODE_ENV=production MINIFY=true cross-env webpackrelease:unminifiednpm run clean && NODE_ENV=production MINIFY=false cross-env webpackscreenshotsnode scripts/screenshots.mjsstartwebpack servertestvitesttest:coveragevitest run --coveragetest:runvitest run
Dependencies8
@babel/runtime^7.29.2@fullcalendar/core^6.1.20@fullcalendar/daygrid^6.1.20@fullcalendar/interaction^6.1.20@fullcalendar/list^6.1.20@fullcalendar/timegrid^6.1.20chart.js^4.5.1jsvectormap^1.7.0