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
- 583
- Versions published
- 9
- First published
- Feb 2026
- Publisher
- giampiero_sp
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":["@studyportals/[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":["@studyportals/[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
Scripts9
compilerm -fR bin && npx tsc && npx tsc-alias -p tsconfig.json --outDir bin -fdeploynpm run prepare-deployment && npm publish ./bindeploy-betanpm version prerelease && npm run prepare-deployment && npm publish ./bin --tag betadeploy-majornpm version major && npm run deploydeploy-minornpm version minor && npm run deploydeploy-patchnpm version patch && npm run deploylinteslint . --ext .tslint:fixeslint . --ext .ts --fixprepare-deploymentnpm run compile && cp package.json bin/package.json