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
- 14
- First published
- Mar 2026
- Publisher
- axel-dev
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":["@ws-ui/[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":["@ws-ui/[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 && vite build && npm run build:styles:standalonebuild:styles:standalonenpx postcss src/Standalone/style.css -o dist/Standalone/style.css --config ./postcss.config.scoped.js --no-mapdevviteprepacknpm run buildpublishyarn npm publish --access public
Dependencies14
@emotion/react^11.4.0@emotion/styled^11.14.0@headlessui/react^1.7.19@ws-ui/icons1.13.0@ws-ui/shared1.13.0-rc1@ws-ui/store1.13.0-rc1classnames^2.3.1downshift^6.1.3framer-motion^4.1.17lodash^4.17.21path-browserify^1.0.1react^17.0.2react-dom^17.0.2react-select^5.8.0