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
- 25
- First published
- Apr 2026
- Publisher
- samtolmay
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":["@lowdefy/[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":["@lowdefy/[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
buildswc src --out-dir dist --config-file ../../../../.swcrc --cli-config-file ../../../../.swc-cli.json && pnpm copyfilescleanrm -rf distcopyfilescopyfiles -u 1 "./src/**/*" dist -e "./src/**/*.js" -e "./src/**/*.yaml" -e "./src/**/*.snap"e2eplaywright test --config e2e/playwright.config.jse2e:uiplaywright test --config e2e/playwright.config.js --ui
Dependencies8
@ant-design/icons6.1.0@lowdefy/block-utils0.0.0-experimental-20260612081926@lowdefy/helpers0.0.0-experimental-20260612081926dayjs1.11.19diff5.2.2microdiff1.4.0pluralize8.0.0yaml2.3.4