PkgRadar

Package evidence

@quannh1511/[email protected]

Suspicious Publish Context: {"package_age_days":1,"publisher":"quannh1511","burst_same_day":0,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}

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
2
First published
Jun 2026
Publisher
quannh1511

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":["@quannh1511/[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":["@quannh1511/[email protected]"],"fail_on":"review"}'
Publisherquannh1511
Artifact bytes46,485
Previous version2.1.0
Published2026-06-15T14:50:18.278Z
SHA-256fe63faced04f0b094267fc366e0c4bcddc78d4510f05e12bac0e0cba1fab23ac

Why flagged

What the scanner saw

Suspicious Publish Context: {"package_age_days":1,"publisher":"quannh1511","burst_same_day":0,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}

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

Availability ledger

available

review
Last checked
reviewRisk
10Score
2.1.1Version
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":1,"publisher":"quannh1511","burst_same_day":0,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}10

Manifest

Package metadata

Scripts13
  • buildtsc -p tsconfig.build.json
  • build:verifynpm run build && node -e "const fs=require('fs'),p=require('path');function walk(d){const r=[];for(const f of fs.readdirSync(d,{withFileTypes:true})){const fp=p.join(d,f.name);if(f.isDirectory())r.push(...walk(fp));else if(f.name.endsWith('.js'))r.push(fp)}return r}const files=walk('dist');const found=files.some(f=>fs.readFileSync(f,'utf8').includes('__decorate'));if(!found){console.error('FAIL: no decorator compilation (__decorate) found in dist/');process.exit(1)}console.log('OK: decorator metadata present (__decorate found in '+files.length+' files)')"
  • formatprettier --write "src/**/*.ts" "tests/**/*.ts"
  • format:checkprettier --check "src/**/*.ts" "tests/**/*.ts"
  • linteslint src/ tests/
  • lint:fixeslint src/ tests/ --fix
  • pack:drynpm pack --dry-run
  • prepublishOnlynpm run build
  • publish:ghcp .npmrc .npmrc.bak && printf '@nguyenhoangquan1511-dot:registry=https://npm.pkg.github.com\n' > .npmrc && npm publish; STATUS=$?; mv .npmrc.bak .npmrc; exit $STATUS
  • publish:npmnpm publish
  • testjest
  • test:covjest --coverage
  • test:watchjest --watch
Dependencies4
  • nestjs-pino^4.6.1
  • pino^9.14.0
  • pino-http^10.5.0
  • tslib^2.8.1