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
- 4
- First published
- Jun 2026
- Publisher
- nandoo-kim
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":["@ninebone/[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":["@ninebone/[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
Scripts4
buildecho '빌드가 필요한 프로젝트라면 여기에 빌드 명령 작성'devnode --watch src/index.jsreleasenpm version patch && npm run build && npm publishstartnode src/index.js
Dependencies12
@langchain/core^1.1.44@langchain/google-genai^2.1.30@modelcontextprotocol/sdk^1.29.0@nine-lab/nine-util^0.9.35cors^2.8.6dotenv^16.4.5express^4.22.1mariadb^3.5.2mysql2^3.9.7oracledb^6.10.0pg^8.11.5ws^8.20.1