PkgRadar

Package evidence

@telaro/[email protected]

Suspicious Publish Context: {"package_age_days":0,"publisher":"kreolabs","burst_same_day":2,"burst_week":2,"lure":null,"version_anomaly":false,"new_account":false}

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
1
First published
Jun 2026
Publisher
kreolabs

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

Inspect tarballAdd to CI gate
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"}'
Publisherkreolabs
Artifact bytes2,093
Previous versionnone
Published2026-06-16T02:04:43.439Z
SHA-256b17ed6b95b8ee6b44adc472bef29c6b0dcd791c3eaf2fb459f733d584ae7839c

Why flagged

What the scanner saw

Suspicious Publish Context: {"package_age_days":0,"publisher":"kreolabs","burst_same_day":2,"burst_week":2,"lure":null,"version_anomaly":false,"new_account":false}

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review
Last checked
reviewRisk
10Score
0.1.0Version
Status history (2 events)
  1. scan_error → available · risk review · score 10 · status scan_error -> available, risk none -> review, score none -> 10
  2. new → scan_error · risk none · score — · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/@telaro/buzz/-/buzz-0.1.0.tgz)

Evidence

Static findings

1 static · 0 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
mediumSuspicious Publish Contextmanifest{"package_age_days":0,"publisher":"kreolabs","burst_same_day":2,"burst_week":2,"lure":null,"version_anomaly":false,"new_account":false}10

Manifest

Package metadata

Scripts4
  • buildtsc -p tsconfig.json
  • cleanrm -rf dist
  • testnode --import tsx/esm --test --test-concurrency=1 tests/*.test.ts
  • typechecktsc --noEmit
Dependencies3
  • @solana/web3.js^1.95.0
  • @telaro/framework-adapter-core0.1.0
  • @telaro/sdk0.1.17