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
- 481
- Versions published
- 270Mature · −50% score
- First published
- Sep 2018
- Publisher
- zhangzhenyu_125306
Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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":["[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"}'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
Scripts7
buildrimraf lib && mkdirp lib && cross-env webpack --progress --hide-modules --config build/webpack.prod.conf.jsdevnode build/dev-server.jse2enode test/e2e/runner.jsexamplenode build/example-server.jslinteslint src/**.js test/e2e/**.js test/unit/specs/** build/**.jsreleasenpm set registry http://registry.npmjs.org && npm publish && npm set registry http://registry.npm.taobao.orgunitcross-env BABEL_ENV=test karma start test/unit/karma.conf.js --single-run
Dependencies10
jquery^3.3.1less^2.7.3less-loader^2.2.3marked2.1.3style0.0.3style-loader^0.21.0vue^1.0.17vue-cli^2.9.6vue-devtools^4.1.4vue-resource^1.5.1