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
- 651
- Versions published
- 6
- First published
- May 2026
- Publisher
- linfaxin
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":["@1game/[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":["@1game/[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
buildpnpm run clean && pnpm run typecheck && pnpm run build:bundlebuild:bundlenode ./scripts/bundle.mjscleanrimraf dist tsconfig.tsbuildinfoprepublishpnpm run buildtestpnpm run typecheck && pnpm run test:unit && pnpm run test:e2etest:e2eplaywright test -c playwright.config.tstest:unitvitest runtest:watchvitesttypechecktsc -p tsconfig.json --noEmit
Dependencies8
@1game/1gamerecord-player-html1.3.0@1game/cli1.3.0@1game/engine-bundle1.3.0better-sqlite3^12.6.2memfs^4.51.1playwright^1.58.1solid-js^1.9.0sql.js^1.14.1