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
- 763
- Versions published
- 75
- 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
buildtsupcleanrm -rf distdevtsup --watchprepublishOnlynpm run buildtype-checktsc --noEmit
Dependencies15
@lark-apaas/client-capability0.1.7-alpha.2@lark-apaas/dataloom^0.1.1@lark-apaas/internal-slardar^0.0.3@lark-apaas/miaoda-inspector^1.0.23@lark-apaas/observable-web^1.0.6@radix-ui/react-dialog^1.0.5@radix-ui/react-popover^1.0.7axios^1.12.2blueimp-md5^2.10.0clsx^2.0.1crypto-js^3.1.9-1lodash^4.17.21penpal^6.2.2stacktrace-js^2.0.2tailwind-merge^2.0.0