PkgRadar

Package evidence

@stackone/[email protected]

no findings

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
59Established · −30% score
First published
Jul 2025
Publisher
stackone-publisher

Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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":["@stackone/[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":["@stackone/[email protected]"],"fail_on":"review"}'
Publisherstackone-publisher
Artifact bytes1,028,034
Previous version1.10.1
Published2026-06-16T11:04:22.019Z
SHA-2569e1eb658d037d94033913a0fdfdce3bd86fb9b835c361b90f4e03f5ccf43045c

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

low
Last checked
lowRisk
0Score
1.10.2Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts27
  • buildrollup -c
  • code:formatbiome format ./src ./dev
  • code:format:fixbiome format --write ./src ./dev
  • devcd dev/vite && npm run dev
  • dev:angularcd dev/angular && npm run dev
  • dev:angular:setupnpm run build && cd dev/angular && npm install
  • dev:nextjscd dev/nextjs && npm run dev
  • dev:nextjs:setupnpm run build && cd dev/nextjs && npm install
  • dev:react-wccd dev/react && npm run dev
  • dev:react-wc:setupnpm run build && cd dev/react && npm install
  • dev:react19cd dev/vite-react19 && npm run dev
  • dev:react19:setupnpm run build && cd dev/vite-react19 && npm install
  • dev:rsbuildcd dev/rsbuild && npm run dev
  • dev:rsbuild:buildcd dev/rsbuild && npm run build
  • dev:rsbuild:setupnpm run build && cd dev/rsbuild && npm install
  • dev:setupnpm run build && cd dev/vite && npm install
  • dev:sveltecd dev/svelte && npm run dev
  • dev:svelte:setupnpm run build && cd dev/svelte && npm install
  • dev:vanillacd dev/vanilla && npm run dev
  • dev:vanilla:setupnpm run build && cd dev/vanilla && npm install
  • dev:vuecd dev/vue && npm run dev
  • dev:vue:setupnpm run build && cd dev/vue && npm install
  • lintbiome lint --error-on-warnings ./src ./dev && biome check ./src ./dev
  • lint:fixbiome lint --write ./src ./dev && biome check --write ./src ./dev
  • publish-releasenpm publish --access=public
  • relaycd dev/vite && npm run relay
  • testecho "Error: no test specified" && exit 1
Dependencies3
  • @stackone/malachite^0.25.2
  • @tanstack/react-query^5.77.2
  • use-deep-compare-effect^1.8.1