PkgRadar

Package evidence

[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
5
First published
May 2026
Publisher
macieju-opera

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":["[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":["[email protected]"],"fail_on":"review"}'
Publishermacieju-opera
Artifact bytes3,133,494
Previous version0.2.3
Published2026-06-11T13:22:14.233Z
SHA-2567ca30644443cf69399ebd3076fb900aa9a64c8542fc8e1fcc6af490df6dd7fdf

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

Scripts22
  • buildtsc && node --experimental-strip-types --no-warnings=ExperimentalWarning scripts/post-build.ts
  • bundlenpm run clean && npm run build && rollup -c rollup.config.mjs && node -e "require('fs').rmSync('build/node_modules', {recursive: true, force: true})" && node --experimental-strip-types scripts/append-lighthouse-notices.ts
  • check-formateslint --cache . && prettier --check --cache .;
  • cleannode -e "require('fs').rmSync('build', {recursive: true, force: true})"
  • cli:generatenode --experimental-strip-types scripts/generate-cli.ts
  • count-tokensnode --experimental-strip-types scripts/count_tokens.ts
  • docs:generatenode --experimental-strip-types scripts/generate-docs.ts
  • evalnpm run build && node --experimental-strip-types scripts/eval_gemini.ts
  • formateslint --cache --fix . && prettier --write --cache .
  • gennpm run build && npm run docs:generate && npm run cli:generate && npm run update-tool-call-metrics && npm run format
  • preparenode --experimental-strip-types scripts/prepare.ts
  • startnpm run build && node build/src/bin/chrome-devtools-mcp.js
  • start-debugDEBUG=mcp:* DEBUG_COLORS=false npm run build && node build/src/bin/chrome-devtools-mcp.js
  • testnpm run build && node scripts/test.mjs
  • test:no-buildnode scripts/test.mjs
  • test:onlynpm run build && node scripts/test.mjs --test-only
  • test:update-snapshotsnpm run build && node scripts/test.mjs --test-update-snapshots
  • typechecktsc --noEmit
  • update-lighthousenode --experimental-strip-types scripts/update-lighthouse.ts
  • update-tool-call-metricsnode --experimental-strip-types scripts/update_tool_call_metrics.ts
  • verify-npm-packagenode scripts/verify-npm-package.mjs
  • verify-server-json-versionnode --experimental-strip-types scripts/verify-server-json-version.ts