PkgRadar

Package evidence

@synanetics/[email protected]

Install-time lifecycle script: preinstall="npx only-allow pnpm"

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
7
First published
Jun 2024
Publisher
synrichardbrown

Recommended action

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

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":["@synanetics/[email protected]"],"fail_on":"high"}'

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":["@synanetics/[email protected]"],"fail_on":"high"}'
Publishersynrichardbrown
Artifact bytes865,965
Previous version1.0.1
Published2026-05-26T10:08:23.312Z
SHA-25600601c4fcdb7c598c4ff934e1664ff808002186d58bace7101e269ffeb7f2681

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 1.0.2 vs 1.0.1: "npx only-allow pnpm"

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

Availability ledger

available

high
Last checked
highRisk
45Score
1.0.2Version
Status history (1 event)
  1. new → available · risk high · score 45 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 1.0.2 vs 1.0.1: "npx only-allow pnpm"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 1.0.2 vs 1.0.1: "npx only-allow pnpm"40
lowInstall-time lifecycle scriptpackage.jsonpreinstall="npx only-allow pnpm"5

Manifest

Package metadata

Scripts4
  • preinstallnpx only-allow pnpm
  • preparetsdown --config ../../tsdown.config.ts
  • prepublishpnpm run build
  • testjest --coverage
Dependencies1
  • fhirpath^3.13.0