PkgRadar

Package evidence

@oresoftware/[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
24Mature · −50% score
First published
Jun 2018
Publisher
oresoftware

Effective trust discount applied: −50% (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":["@oresoftware/[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":["@oresoftware/[email protected]"],"fail_on":"review"}'
Publisheroresoftware
Artifact bytes7,588
Previous version2.2.13
Published2026-06-02T15:53:12.724Z
SHA-2566ee899c90302f1a1ef8cd0ce89af3b331d8e0917ec5569d9a23ffc67cf9f6523

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
3.1.12Version
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

Scripts10
  • buildtsc && node scripts/write-package-boundaries.cjs && tsc -p tsconfig.esm.json && node scripts/write-package-boundaries.cjs
  • testnode --test test/node-test/*.test.js
  • test:allnpm run test && npm run test:internal:standalone && npm run test:legacy
  • test:corenode --test test/node-test/core.test.js
  • test:edgenode --test test/node-test/edge-cases.test.js
  • test:fuzznode --test test/node-test/fuzz.test.js
  • test:internalnode --test test/node-test/internal.test.js
  • test:internal:standalonenode test/internal/linked-list-integrity.js && node test/internal/head-tail-fuzz.js && node test/internal/lookup-consistency.js
  • test:iteratorsnode --test test/node-test/iterators.test.js
  • test:legacynode test/src/test-fuzz.js && node test/src/linked-queue-fuzz.js && node test/src/queue-fuzz.js && node test/src/basic-queue-fuzz.js