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
- 81
- Versions published
- 12
- First published
- Mar 2026
- Publisher
- aolteanuipath
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["@uipath/[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":["@uipath/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Large Javascript Payload: 3095628 bytes
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 review · score 30 · status changed
Evidence
Static findings
3 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Large Javascript Payload | package/dist/packager-tool.js | 3095628 bytes | 10 |
| medium | Large Javascript Payload | package/dist/tool.js | 9702801 bytes | 10 |
| medium | Large Javascript Payload | package/dist/validation.js | 3462554 bytes | 10 |
Manifest
Package metadata
Scripts7
buildbun ../../tools/build-tool.ts && bun build ./src/validation.ts --outdir dist --format esm --target node && tsc -p tsconfig.build.json --noChecklintbiome check .lint:fixbiome check --write .packagebun run build && bun pm packtestvitest run && vitest run -c vitest.isolated.config.tstest:coveragevitest run --coverage && vitest run --coverage -c vitest.isolated.config.ts && cat coverage-isolated/lcov.info >> coverage/lcov.info && rm -rf coverage-isolatedtest:isolatedvitest run -c vitest.isolated.config.ts