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
- 67
- First published
- Apr 2026
- Publisher
- duanlikang_byte
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":["@lark-apaas/[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":["@lark-apaas/[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
Scripts5
buildtsc || trueprepublishOnlynpm run buildtestvitest runtest:watchvitestwatchtsc --watch
Dependencies14
@lark-apaas/devtool-kits^1.2.23@tailwindcss/vite^4.0.0@vitejs/plugin-react^6.0.0clsx^2.1.1colorjs.io^0.5.2core-js^3.40.0dotenv^16.4.5echarts^6.0.0echarts-for-react^3.0.2glob^11.0.0html-minifier-terser^7.2.0magic-string^0.30.0postcss-import^16.1.1tailwind-merge^2.5.5