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
96Mature · −50% score
First published
Apr 2025
Publisher
itwcw2000

Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

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"}'
Publisheritwcw2000
Artifact bytes226,104
Previous version1.5.0
Published2026-06-11T08:23:48.910Z
SHA-256ac55439e6d2e07f410d3e8a2bfc7ae9d97409247bcdc3840a166440eb5c6ee17

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.6.0Version
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

Scripts6
  • preparenode -e "require('prepare-package')()"
  • prepare:watchnode -e "require('prepare-package/watch')()"
  • startnpm run prepare:watch
  • testnode ./bin/browser-extension-manager test
  • wm:localnpm uninstall web-manager && npm i ../web-manager
  • wm:prodnpm uninstall web-manager && npm i web-manager@latest
Dependencies27
  • @anthropic-ai/claude-agent-sdk^0.2.138
  • @babel/core^7.29.7
  • @babel/preset-env^7.29.7
  • @popperjs/core^2.11.8
  • babel-loader^10.1.1
  • chalk^5.6.2
  • dotenv^17.4.2
  • fs-jetpack^5.1.0
  • glob^13.0.6
  • gulp-clean-css^4.3.0
  • gulp-filter^10.0.0
  • gulp-rename^2.1.0
  • gulp-responsive-modern^1.0.0
  • gulp-sass^6.0.1
  • itwcw-package-analytics^1.0.8
  • json5^2.2.3
  • lodash^4.18.1
  • minimatch^10.2.5
  • node-powertools^3.0.0
  • npm-api^1.0.1
  • sass^1.100.0
  • web-manager^4.2.0
  • webpack^5.107.2
  • wonderful-fetch^2.0.5
  • wonderful-version^1.3.2
  • ws^8.21.0
  • yargs^18.0.0