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
- 912
- Versions published
- 14
- First published
- Jun 2026
- Publisher
- pingid
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":["@lickle/[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":["@lickle/[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
Scripts3
buildpnpm tsc -b -ftestvitest run --exclude '**/dist/**'test:watchvitest --exclude '**/dist/**'
Dependencies24
@lickle/cn^0.0.1@lickle/is0.1.0-dev.14@orama/orama^3.1.18@solidjs/router^0.16.1@tailwindcss/vite^4.3.0cmd-ts^0.15.0codejar^4.3.0execa^9.6.1fast-glob^3.3.3get-tsconfig^4.14.0hosted-git-info^10.1.1jiti^2.7.0marked^18.0.4micromatch^4.0.8picocolors1.1.1pkg-exports^0.2.0resolve.exports^2.0.3shiki^4.2.0solid-js^1.9.13sucrase^3.35.1tailwindcss^4.3.0typescript^6.0.3vite^8.0.16vite-plugin-solid^2.11.12