Package evidence

@protovoters/[email protected]

Install-time lifecycle script: install="node-gyp-build"

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.

Weekly downloads: 30
Versions published: 12Established · −30% score
First published: Nov 2025
Publisher: reesericci

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

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

Inspect tarball Add 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":["@protovoters/[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":["@protovoters/[email protected]"],"fail_on":"review"}'

Publisherreesericci

Artifact bytes3,822,808

Previous version0.7.1

Published2026-04-23T06:35:16.511Z

SHA-25621cd7d53c97d68e5731fa023e7e981613f41318dfa80afcfe068637ca4bbd965

Why flagged

What the scanner saw

Install-time lifecycle script: install="node-gyp-build"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review

8h agoLast checked

reviewRisk

3Score

0.7.2Version

Status history (1 event)

new → available8h ago · risk review · score 3 · status changed

Evidence

Static findings

1 static · 0 from release diff · showing high-signal first.

No high-signal findings — see all findings below.

Show all 1 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
low	Install-time lifecycle script	package.json	install="node-gyp-build"	5

Manifest

Package metadata

Scripts11

buildnode-gyp rebuild
build-osmxbash -c 'cd OSMExpress && find . -name CMakeCache.txt -delete && cmake -DCMAKE_CXX_STANDARD=17 . && make -j$(nproc 2>/dev/null || sysctl -n hw.ncpu)'
cleannode-gyp clean
installnode-gyp-build
prebuildnode -e ""
prebuild:darwinbash -lc 'PY=$(command -v python3.13 || command -v python3.12 || command -v python3.11 || command -v python3); export PYTHON="$PY" npm_config_python="$PY"; prebuildify --napi --strip && (find prebuilds/darwin-* -maxdepth 0 -type d -exec cp OSMExpress/osmx {}/osmx \; || true)'
prebuild:linuxnode scripts/prebuild-linux.mjs
publishyarn npm publish --access public
submodulebash -c 'if [ -d ../../.git ]; then git submodule update --init --recursive OSMExpress; elif [ ! -d OSMExpress/include ]; then if [ -d OSMExpress ]; then tmpdir=$(mktemp -d) && git clone --depth 1 https://github.com/bdon/OSMExpress "$tmpdir" && cp -a "$tmpdir/." OSMExpress/ && rm -rf "$tmpdir"; else git clone --depth 1 https://github.com/bdon/OSMExpress OSMExpress; fi; fi && if [ ! -d OSMExpress/vendor/s2geometry/src ]; then if [ -d ../../.git ]; then git submodule update --init --recursive OSMExpress/vendor/s2geometry; else tmpdir=$(mktemp -d) && git clone --depth 1 https://github.com/google/s2geometry "$tmpdir" && cp -a "$tmpdir/." OSMExpress/vendor/s2geometry/ && rm -rf "$tmpdir"; fi; fi'
testvitest run --passWithNoTests
turboyarn exec turbo

Dependencies2

node-addon-api^8.5.0
node-gyp-build^4.8.0