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
- 1
- First published
- May 2026
- Publisher
- navnry
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":["@tooto-tech/[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":["@tooto-tech/[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 (2 events)
- new → available · risk low · score 0 · status changed
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts5
buildrun-s build-only type-check build-style-typesbuild-onlyvite buildbuild-style-typesnode ./scripts/write-style-types.mjstestvitest runtype-checkvue-tsc --build --force
Dependencies13
@codemirror/lang-css^6.3.1@codemirror/lang-html^6.4.11@codemirror/lang-javascript^6.2.5@codemirror/state^6.6.0@codemirror/theme-one-dark^6.1.3@iconify/vue^5.0.0@lottiefiles/dotlottie-wc^0.9.14@vueuse/core^14.2.1codemirror^6.0.2grapesjs^0.22.16js-beautify^1.15.4postcss8.5.10vue-codemirror^6.1.1