PkgRadar

npm · registry.npmjs.org

@vinnxcode/xbails

New Account With Lifecycle Hook: package first published 0 day(s) ago, 3 total version(s), has lifecycle hook

Why PkgRadar flagged 1.0.2

SeveritySignalEvidence
highNew Account With Lifecycle Hookpackage first published 0 day(s) ago, 3 total version(s), has lifecycle hook · package.json
mediumRemote Dependency Specdependencies.libsignal="github:tenka-san/libsignal-node" · package.json
mediumSuspicious Publish Context{"package_age_days":0,"publisher":"vinnxcode","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}
mediumRemote Dependency SpecdevDependencies.@adiwajshing/eslint-config="github:adiwajshing/eslint-config" · package.json

Scanned versions

VersionVerdictScoreScanned (UTC)
1.0.2High risk352026-06-16
1.0.0High risk352026-06-16
1.0.1High risk352026-06-16

Block this in CI

PkgRadar gates @vinnxcode/xbails (and every other dependency) before it merges. One line in your pipeline:

pkgradar gate --ecosystem npm @vinnxcode/[email protected]