PkgRadar

Package evidence

[email protected]

Suspicious Publish Context: {"package_age_days":0,"publisher":"brahimtimezghine","burst_same_day":2,"burst_week":9,"lure":null,"version_anomaly":false,"new_account":false}

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
1
First published
Jun 2026
Publisher
brahimtimezghine

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

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"}'
Publisherbrahimtimezghine
Artifact bytes77,322
Previous versionnone
Published2026-06-16T13:50:10.201Z
SHA-2562156a7065bd658ad2c75689c902e43c44e80d451a13d871dac82b2f310e17c5b

Why flagged

What the scanner saw

Suspicious Publish Context: {"package_age_days":0,"publisher":"brahimtimezghine","burst_same_day":2,"burst_week":9,"lure":null,"version_anomaly":false,"new_account":false}

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

Availability ledger

available

review
Last checked
reviewRisk
10Score
1.0.0Version
Status history (1 event)
  1. new → available · risk review · score 10 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
mediumSuspicious Publish Contextmanifest{"package_age_days":0,"publisher":"brahimtimezghine","burst_same_day":2,"burst_week":9,"lure":null,"version_anomaly":false,"new_account":false}10

Manifest

Package metadata

Scripts20
  • build:docsnode scripts/buildDocs.js
  • db:resetnode scripts/migrate.js --reset && node scripts/seed.js
  • devnodemon src/index.js
  • dev:debugNODE_OPTIONS='--inspect' nodemon src/index.js
  • formatprettier --write "src/**/*.js" "tests/**/*.js"
  • healthnode -e "import('./src/index.js').then(m => m.healthCheck())"
  • linteslint src/ tests/ --ext .js
  • lint:fixeslint src/ tests/ --ext .js --fix
  • migratenode scripts/migrate.js
  • migrate:undonode scripts/migrate.js --undo
  • seednode scripts/seed.js
  • setupnode scripts/setup.js
  • startnode src/index.js
  • testjest --runInBand
  • test:coveragejest --coverage --coverageDirectory=coverage
  • test:e2ejest tests/e2e --runInBand
  • test:integrationjest tests/integration --runInBand
  • test:unitjest tests/unit --runInBand
  • test:watchjest --watch
  • validate:envnode -e "import('./src/config/constants.js').then(m => m.validateEnv())"
Dependencies35
  • axios^1.6.2
  • bcryptjs^2.4.3
  • compression^1.7.4
  • cors^2.8.5
  • crypto-js^4.2.0
  • date-fns^3.0.0
  • date-fns-tz^2.0.0
  • dotenv^16.3.1
  • express^4.18.2
  • express-async-errors^3.1.1
  • express-rate-limit^7.1.0
  • express-slow-down^2.0.0
  • express-validator^7.0.1
  • helmet^7.1.0
  • ioredis^5.3.2
  • joi^17.11.0
  • jsonwebtoken^9.0.2
  • lru-cache^10.1.0
  • mongoose^8.0.0
  • mongoose-lean-virtuals^0.9.1
  • mongoose-paginate-v2^1.8.1
  • morgan^1.10.0
  • ms^2.1.3
  • nanoid^5.0.4
  • node-cron^3.0.3
  • nodemailer^6.9.7
  • p-queue^8.0.1
  • pino^8.17.0
  • pino-pretty^10.3.0
  • redis^4.6.11
  • …and 5 more.