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.
- Versions published
- 1
- First published
- Jun 2026
- Publisher
- kingdaryush1
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":["@synchronized-console/[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":["@synchronized-console/[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
Scripts11
buildNODE_ENV=production rollup --configbuild:devrollup --configdevrollup --config --watchlintyarn lint:js && yarn lint:tsclint:ciyarn lint:tsclint:jseslint .lint:tsctsc --noEmitprepackyarn buildtestvitesttest:runvitest runtest:uivitest --ui
Dependencies14
@synchronized-console/objectloader2^2.25.7@synchronized-console/shared^2.25.7@types/flat^5.0.2earcut3.0.1flat^5.0.2js-logger1.6.1lodash-es^4.17.21polylabel2.0.1string-to-color^2.2.2three^0.140.0three-mesh-bvh0.5.17tree-model1.0.7troika-three-text0.47.2type-fest^4.15.0