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
28
First published
Apr 2026
Publisher
jetienne

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"}'
Publisherjetienne
Artifact bytes450,819
Previous version1.0.39
Published2026-06-01T23:29:41.953Z
SHA-2566b664ac155d85446e2fa4b35174dc211f2f1de8c2913549bf8c67a7f3e24f6e7

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

Scripts18
  • buildtsc -p tsconfig.build.json
  • clean:output:logrm -f outputs/*.log
  • contribs:linkedin:profilenpx tsx ./src/contribs/linkedin_cli/src/cli.ts profile jeromeetienne
  • contribs:twitter:profilenpx tsx ./src/contribs/twitter_cli/src/cli.ts profile jerome_etienne
  • dev:clinpx tsx ./src/fastbrowser_cli/fastbrowser_cli.ts
  • dev:httpdnpx tsx ./src/fastbrowser_httpd/fastbrowser_httpd.ts
  • dev:mcpnpx tsx ./src/fastbrowser_mcp/fastbrowser_mcp.ts
  • inspect:chrome_devtoolsnpx @modelcontextprotocol/inspector npx chrome-devtools-mcp@latest --autoconnect
  • inspect:fastbrowser_mcp:chrome_devtoolsnpx @modelcontextprotocol/inspector npx tsx ./src/fastbrowser_mcp/fastbrowser_mcp.ts mcp_server --mcp_target chrome_devtools
  • inspect:fastbrowser_mcp:playwrightnpx @modelcontextprotocol/inspector npx tsx ./src/fastbrowser_mcp/fastbrowser_mcp.ts mcp_server -v --mcp_target playwright
  • inspect:playwright:cdp_endpointnpx @modelcontextprotocol/inspector npx @playwright/mcp@latest --cdp-endpoint=http://localhost:9222
  • inspect:playwright:chromenpx @modelcontextprotocol/inspector npx @playwright/mcp@latest --cdp-endpoint=chrome
  • inspect:playwright:extensionnpx @modelcontextprotocol/inspector npx @playwright/mcp@latest --extension
  • prepublish:checktest -z "$(git status --porcelain)" || (echo 'Working tree dirty — commit or stash first' && exit 1)
  • publish:allpnpm run prepublish:check && pnpm run build && pnpm run version:bump && pnpm publish --access public
  • testnpx tsx --test 'tests/**/*.test.ts'
  • typechecktsc -p tsconfig.json --noEmit
  • version:bumpnpm version patch --no-git-tag-version && git add package.json && git commit -m "feat: bump version in fastbrowser_cli package.json"
Dependencies10
  • @modelcontextprotocol/sdk^1.29.0
  • a11y_parse^1.0.8
  • chalk^5.6.2
  • commander^12.1.0
  • express^4.21.2
  • minimatch^10.2.5
  • string-argv^0.3.2
  • typescript^6.0.3
  • zod^4.3.6
  • zod-from-json-schema^0.5.2