PkgRadar

Package evidence

@dxtmisha/[email protected]

no findings

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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":["@dxtmisha/[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":["@dxtmisha/[email protected]"],"fail_on":"review"}'
Publisherdxtmisha
Artifact bytes6,434,286
Previous version0.65.1
Published2026-05-24T15:23:01.547Z
SHA-256206c476365aef8e5294c990ce59b841389bef52bb01010a7a2f68b1567c93218

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

low
Last checked
lowRisk
0Score
0.67.0Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts10
  • buildvue-tsc -b && vite build
  • build-recoverynpm run build && npm run wiki-storm
  • devvite
  • prepublishOnlynpm run ui && npm run build && npm run wiki-storm
  • previewvite preview
  • publish-to-npmnpm publish --access public
  • screenshotdxt-screenshot
  • typesdxt-types
  • uidxt-ui
  • wiki-stormdxt-wiki-storm