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
- 524
- Versions published
- 8
- First published
- May 2026
- Publisher
- kreolabs
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":["@telaro/[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":["@telaro/[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
Scripts6
buildtsc -p tsconfig.jsoncleanrm -rf distprepublishOnlypnpm clean && pnpm buildpublish:drynpm publish --dry-runtestnode --import tsx/esm --test --test-concurrency=1 tests/*.test.tstypechecktsc --noEmit
Dependencies9
@coral-xyz/anchor^0.30.1@metaplex-foundation/mpl-core^1.1.1@metaplex-foundation/umi^0.9.2@metaplex-foundation/umi-bundle-defaults^0.9.2@metaplex-foundation/umi-signer-wallet-adapters^0.9.2@metaplex-foundation/umi-web3js-adapters^0.9.2@noble/hashes^1.5.0@solana/spl-token^0.4.8@solana/web3.js^1.95.0