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
- 9
- First published
- Sep 2022
- Publisher
- tiebyte
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":["@volcengine/[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":["@volcengine/[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
Scripts8
buildrm -rf lib && tscjson-schema-buildercross-env node ./scripts/schema.jslinteslint src --ext .ts --fixlint-stagedlint-stagedpreparehusky installprettierprettier --write "src/**/*.ts"testyarn build && jest --env=nodetest-covyarn build && jest --env=node --coverage
Dependencies13
ajv^8.11.0axios^0.27.2crypto-js^4.1.1dayjs^1.11.5debug^4.3.4form-data^4.0.0lodash.get^4.4.2lodash.merge^4.6.2lodash.omit^4.5.0lodash.pick^4.4.0mime-db^1.52.0query-string^7.1.1uuid^8.3.2