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
- 36
- Versions published
- 5
- First published
- Jun 2026
- Publisher
- aself101
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":["@uluops/[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":["@uluops/[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
Scripts14
buildtsccleanrm -rf distdevtsx watch src/index.tsformatprettier --write "src/**/*.ts"format:checkprettier --check "src/**/*.ts"linteslint src/postbuildchmod +x dist/index.jsprebuildnpm run cleanprepublishOnlynpm run buildstartnode dist/index.jstestvitest runtest:coveragevitest run --coveragetest:watchvitesttypechecktsc --noEmit
Dependencies5
@modelcontextprotocol/sdk1.29.0@uluops/registry-sdk0.30.2@uluops/sdk-core0.11.1mcp-secure-server0.0.14-securityzod3.25.76