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
- 78
- First published
- Mar 2026
- Publisher
- reion
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":["@m5kdev/[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":["@m5kdev/[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
buildtsdowncheck-typestsc --noEmitlintbiome check .lint:fixbiome check . --writeversion:patchnpm version patch
Dependencies15
@aws-sdk/s3-request-presigner3.891.0@internationalized/date3.8.2@m5kdev/commons0.20.48@react-types/calendar3.8.3@react-types/shared3.33.1@tanstack/react-query5.83.0@trpc/client11.4.3@trpc/tanstack-react-query11.4.3better-auth1.4.18luxon3.7.1nuqs2.4.3posthog-js1.258.2react19.2.1react-dom19.2.1zod4.2.1