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
- 71
- Versions published
- 13
- First published
- May 2026
- Publisher
- liweisum
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":["@godscene/[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":["@godscene/[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
Scripts8
buildnpm run build:script && npm run build:pkgbuild:pkgrslib buildbuild:scriptrslib build -c ./rslib.inspect.config.tsbuild:watchnpm run build:script && rslib build --watch --no-cleandevnpm run build:watchresetrimraf ./**/node_modulestestvitest --runtest:uvitest --run -u
Dependencies10
@modelcontextprotocol/sdk1.10.2@silvia-odwyer/photon0.3.3@silvia-odwyer/photon-node0.3.3debug4.4.0dotenv^16.4.5express^4.21.2js-sha2560.11.0sharp^0.34.3uuid11.1.0zod^3.25.1