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
368Mature · −50% score
First published
Jan 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 bytes5,219,561
Previous version1.8.0
Published2026-06-11T10:21:55.807Z
SHA-25680f8dbf4b0c9ee65260e7b93820f5ef8162013241eab0a707851d5012f2fd4d2

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.8.1Version
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/ultimate-jekyll test
  • wm:localnpm uninstall web-manager && npm i ../web-manager
  • wm:prodnpm uninstall web-manager && npm i web-manager@latest
Dependencies45
  • @babel/core^7.29.7
  • @babel/preset-env^7.29.7
  • @fullhuman/postcss-purgecss^8.0.0
  • @minify-html/node^0.18.1
  • @octokit/rest^22.0.1
  • @popperjs/core^2.11.8
  • @prettier/plugin-xml^3.4.2
  • adm-zip^0.5.17
  • babel-loader^10.1.1
  • browser-sync^3.0.4
  • chalk^5.6.2
  • chart.js^4.5.1
  • cheerio^1.2.0
  • chrome-launcher^1.2.1
  • dompurify^3.4.6
  • dotenv^17.4.2
  • fast-xml-parser^5.8.0
  • fs-jetpack^5.1.0
  • glob^13.0.6
  • gulp-clean-css^4.3.0
  • gulp-filter^10.0.0
  • gulp-postcss^10.0.0
  • gulp-rename^2.1.0
  • gulp-responsive-modern^1.0.0
  • gulp-sass^6.0.1
  • html-minifier-terser^7.2.0
  • html-validate^11.4.0
  • itwcw-package-analytics^1.0.8
  • js-yaml^4.1.1
  • json5^2.2.3
  • …and 15 more.