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.
- Weekly downloads
- 2
- Versions published
- 4
- First published
- Dec 2019
- Publisher
- tod.zx
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":["@txdfe/[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":["@txdfe/[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
Scripts5
buildgulp builddemowebpack-dev-server --config ./webpack.demo.js --port 8000 --host 0.0.0.0 --env.developmentdevegg-bin devlinteslint src --fix --ext '.js,.jsx'startNODE_ENV=development bisheng start --config ./site/bisheng.config.js
Dependencies14
@txdfe/at*@txdfe/at-theme*axios^0.19.0core-js^3.4.1debounce^1.2.0hoist-non-react-statics^3.3.0import^0.0.6moment^2.24.0mustache^3.0.1prop-types^15.7.2react^16.8.6react-dom^16.8.6regenerator-runtime^0.13.3systemjs^6.1.4