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
- 11
- First published
- May 2026
- Publisher
- fponticelli
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":["@llui/[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":["@llui/[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
buildtsc -p tsconfig.build.jsonchecktsc --noEmitlinteslint srctestvitest run
Dependencies15
@lexical/code-core^0.45.0@lexical/link^0.45.0@lexical/list^0.45.0@lexical/markdown^0.45.0@lexical/rich-text^0.45.0@lexical/selection^0.45.0@lexical/table^0.45.0@lexical/utils^0.45.0@llui/components^0.11.7@llui/lexical^0.2.4@llui/markdown-editor^0.2.6fflate^0.8.3html-to-image^1.11.13lexical^0.45.0yaml^2.9.0