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
- 43
- Versions published
- 31
- First published
- Mar 2026
- Publisher
- yucekj
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":["[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":["[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
Scripts11
buidnpm run buildbuildtsdown && node ./scripts/generate-schema.mjsformatprettier --write src/**/*.tsformat:checkprettier --check src/**/*.tslinteslint src/ index.tslint:fixeslint src/ index.ts --fixpack:ylib-openclawcd ./lib/openclaw && npm packprepublishOnlynpm run buidpublish:allnpm publish && npm run publish:ylib-openclawpublish:ylib-openclawcd ./lib/openclaw && npm publishreleasenode scripts/release.mjs
Dependencies6
@larksuiteoapi/node-sdk^1.59.0@sinclair/typebox0.34.48image-size^2.0.2marked^15.0.12ylib-openclaw2026.3.9-beta.5zod^4.3.6