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
- 193
- First published
- Feb 2026
- Publisher
- shriyanshacoustte
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":["@acoustte-digital-services/[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":["@acoustte-digital-services/[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
Scripts1
buildtsup
Dependencies45
acorn^8.15.0any-promise^1.3.0bundle-require^5.1.0cac^6.7.14chokidar^4.0.3commander^4.1.1confbox^0.1.8consola^3.4.2csstype^3.2.3debug^4.4.3esbuild^0.27.2fdir^6.5.0fix-dts-default-cjs-exports^1.0.1joycon^3.1.1lilconfig^3.1.3lines-and-columns^1.2.4load-tsconfig^0.2.5magic-string^0.30.21mlly^1.8.0moment-timezone^0.6.2ms^2.1.3mz^2.7.0next^15.5.18object-assign^4.1.1pathe^2.0.3picocolors^1.1.1picomatch^4.0.3pirates^4.0.7pkg-types^1.3.1postcss-load-config^6.0.1- …and 15 more.