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
- 424
- Versions published
- 7
- First published
- May 2026
- Publisher
- pascal_lohscheidt
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":["@m4trix/[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":["@m4trix/[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
Scripts9
buildtsup && vite buildbuild:clientvite buildbuild:servertsupdevvite --host 127.0.0.1formatbiome format --write .lintbiome lint .publish-packagepnpm publish --no-git-checksreleasepnpm -C ../.. run release:bump:trace-viewertestvitest run --config vitest.config.ts
Dependencies10
@aws-sdk/client-dynamodb^3.1053.0@aws-sdk/client-s3^3.1053.0@aws-sdk/lib-dynamodb^3.1053.0@headlessui/react^2.2.0@phosphor-icons/react^2.1.10@trpc/client^11.8.0@trpc/server^11.8.0react^19.1.0react-dom^19.1.0zod^3.23.8