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
- 602
- Versions published
- 73
- First published
- Mar 2026
- Publisher
- stackwright
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":["@stackwright-pro/[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":["@stackwright-pro/[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
buildnode ../../scripts/sync-versions.mjs && tsupdevtsup --watchsync-versionsnode ../../scripts/sync-versions.mjstestvitest runtest:coveragevitest run --coverage
Dependencies12
@stackwright-pro/auth0.2.0-alpha.11@stackwright-pro/auth-nextjs0.2.0-alpha.13@stackwright-pro/mcp0.2.0-alpha.54@stackwright-pro/openapi0.3.0-alpha.23@stackwright-pro/otters1.0.0-alpha.40@stackwright-pro/scaffold-hooks1.0.0-alpha.15@stackwright/cli^0.9.0@stackwright/scaffold-core^0.3.2chalk^5.6.2commander^15.0.0fs-extra^11.3.5js-yaml^4.1.0