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
- 3
- First published
- Nov 2019
- Publisher
- topher.lendi
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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":["@lendi/[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":["@lendi/[email protected]"],"fail_on":"review"}'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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts10
buildtscclits-node --files src/index.tslintyarn lint:other && yarn lint:tslint:fixyarn lint:fix:ts && yarn lint:fix:otherlint:fix:otheryarn prettier --writelint:fix:tsyarn lint:ts --fixlint:otheryarn prettier --list-differentlint:tseslint --ignore-path .gitignore --ignore-path .prettierignore "**/*.ts"prettierprettier "**/*.{json,md,scss,yaml,yml}"testjest
Dependencies5
aws-sdk^2.395.0dotenv^8.2.0inquirer^6.2.1pino^5.13.2yargs^12.0.2