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
- 38
- First published
- Jan 2026
- Publisher
- hsupu
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":["@hsupu/[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":["@hsupu/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched "github_token"
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 | Credential file access | package/dist/main.mjs | matched "github_token" | 10 |
Manifest
Package metadata
Scripts32
buildnpm run build:ui && npm run build:backendbuild:backendnpx tsdownbuild:uivite build --config ui/vite.config.tsdevbun run --watch ./src/main.tsdev:uivite --config ui/vite.config.tsgenerate:config-schemabun run scripts/generate-config-json-schema.tsknipknip-bunlinteslint --cachelint:alleslint --cache .prepacknpm run buildpreparenpm run build && (command -v bun >/dev/null 2>&1 && simple-git-hooks || true)preview:uivite preview --config ui/vite.config.tsreleasebumpp && npm publish --access publicstartNODE_ENV=production bun run ./src/main.tstestnpm run test:backendtest:acceptancenpm run test:backend && npm run test:ui && npm run test:e2e-uitest:allnpm run test:backend && npm run test:uitest:backendbun test .unit.test .it.test .http.testtest:cinpm run test:backendtest:covbun test --coverage .unit.test .it.test .http.testtest:cov:reportbun test --coverage --coverage-reporter lcov .unit.test .it.test .http.testtest:e2ebun test tests/e2e/test:e2e-uibunx playwright testtest:e2e-ui:localPLAYWRIGHT_BASE_URL=http://localhost:4141 bunx playwright testtest:httpbun test .http.testtest:itbun test .it.testtest:uinpm run test:ui:bun && npm run test:ui:vitesttest:ui:bunbun test ./ui/tests/test:ui:vitestvitest run --config ui/vitest.config.tstest:unitbun test .unit.test- …and 2 more.
Dependencies24
@google/genai^2.8.0@hono/node-ws^1.3.1@mdi/font^7.4.47@vueuse/core^14.3.0@vueuse/integrations^14.3.0citty^0.2.2consola^3.4.2diff^9.0.0fetch-event-stream^0.1.6gpt-tokenizer^3.4.0hono^4.12.23picocolors^1.1.1pinia^3.0.4proxy-from-env^2.1.0socks^2.8.9tiny-invariant^1.3.3undici^7.26.0unplugin-auto-import^21.0.0unplugin-vue-components^32.1.0vue^3.5.35vue-json-pretty^2.6.0vue-router^5.1.0vuetify^4.0.8yaml^2.9.0