Package evidence
@gjsify/[email protected]
Suspicious Publish Context: {"package_age_days":0,"publisher":"GitHub Actions","burst_same_day":0,"burst_week":0,"lure":{"kind":"token_affix","target":"platform"},"version_anomaly":false,"new_account":false}
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
- 2
- First published
- Jun 2026
- Publisher
- GitHub ActionsTrusted automation · −70% score
Effective trust discount applied: −70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["@gjsify/[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":["@gjsify/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Suspicious Publish Context: {"package_age_days":0,"publisher":"GitHub Actions","burst_same_day":0,"burst_week":0,"lure":{"kind":"token_affix","target":"platform"},"version_anomaly":false,"new_account":false}
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 review · score 10 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Suspicious Publish Context | manifest | {"package_age_days":0,"publisher":"GitHub Actions","burst_same_day":0,"burst_week":0,"lure":{"kind":"token_affix","target":"platform"},"version_anomaly":false,"new_account":false} | 10 |
Manifest
Package metadata
Scripts11
buildgjsify run build:gjsify && gjsify run build:typesbuild:gjsifygjsify build --library 'src/**/*.{ts,js}' --exclude 'src/**/*.spec.{mts,ts}' 'src/test.{mts,ts}'build:testgjsify run build:test:gjs && gjsify run build:test:nodebuild:test:gjsgjsify build src/test.mts --app gjs --outfile test.gjs.mjsbuild:test:nodegjsify build src/test.mts --app node --outfile test.node.mjsbuild:typesgjsify tsccheckgjsify tsc --noEmitclearrm -rf lib tsconfig.tsbuildinfo tsconfig.types.tsbuildinfo test.gjs.mjs test.node.mjs || exit 0testgjsify run build:gjsify && gjsify run build:test && gjsify run test:node && gjsify run test:gjstest:gjsgjsify run test.gjs.mjstest:nodenode test.node.mjs