Package evidence

@scrapitos/[email protected]

Credential file access: matched "AWS_ACCESS_KEY"

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: 187
Versions published: 17
First published: May 2026
Publisher: scrapitosorg

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

Publisherscrapitosorg

Artifact bytes3,644,088

Previous version1.0.12

Published2026-05-18T05:12:19.616Z

SHA-256227896bc3506aeba57595dc1183724694920637060cad2e033996ec7cf88ac3a

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.0.13 vs 1.0.12: "playwright install chromium"

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

Availability ledger

available

high

7d agoLast checked

highRisk

50Score

1.0.13Version

Status history (1 event)

new → available16d ago · risk high · score 50 · status changed

Evidence

Static findings

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

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 1.0.13 vs 1.0.12: "playwright install chromium"	40

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 1.0.13 vs 1.0.12: "playwright install chromium"	40
low	Credential file access	package/dist/utils/configManager.js	matched "AWS_ACCESS_KEY"	5
low	Install-time lifecycle script	package.json	postinstall="playwright install chromium"	5

Manifest

Package metadata

Scripts4

buildtsc && mkdir -p dist/recorder/scripts && cp recorder/scripts/client.js dist/recorder/scripts/
devts-node cli/agent.ts serve
postinstallplaywright install chromium
startnode dist/cli/agent.js serve

Dependencies12

@google/generative-ai^0.24.1
commander^12.1.0
cors^2.8.5
dotenv^16.4.5
express^4.19.2
mongodb^7.1.1
openai^6.36.0
pino^10.3.1
pino-pretty^13.1.3
pino-roll^4.0.0
playwright^1.59.1
uuid^10.0.0