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
- 7
- First published
- Jun 2026
- Publisher
- aipower_fe
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":["@yingdao-ai/[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":["@yingdao-ai/[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
Scripts20
buildbun x tsc -p tsconfig.jsonchangelog:syncbun scripts/changelog.tsprepacknpm run buildprepare:alphanpm run version:alpha && npm run changelog:syncprepare:betanpm run version:beta && npm run changelog:syncprepare:releasenpm run version:release && npm run changelog:syncpublish:alphanpm publish --tag alpha --access public && npm run sync:npmmirrorpublish:betanpm publish --tag beta --access public && npm run sync:npmmirrorpublish:latestnpm publish --tag latest --access public && npm run sync:npmmirrorrelease:alphabun scripts/release.ts --channel=alpharelease:betabun scripts/release.ts --channel=betarelease:checknpm run build && bun test ./test --timeout 30000 && bun typecheck && npm pack --dry-runrelease:latestbun scripts/release.ts --channel=latestsync:npmmirrorcurl -s -X PUT "https://registry-direct.npmmirror.com/-/package/$npm_package_name/syncs" | node -e "process.stdin.resume();let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{const r=JSON.parse(d);if(r.ok)console.log('npmmirror sync triggered:', r.id);else{console.error('sync failed');process.exit(1)}})"tag:versiongit tag "v$npm_package_version"testbun test ./test --timeout 30000typechecktsgo --noEmitversion:alphanpm version prerelease --preid=alpha --no-git-tag-versionversion:betanpm version prerelease --preid=beta --no-git-tag-versionversion:releasenpm version patch --no-git-tag-version
Dependencies6
@langfuse/otel^5.4.0@langfuse/tracing^5.4.0@opentelemetry/api^1.9.0@opentelemetry/context-async-hooks^2.7.1@opentelemetry/exporter-trace-otlp-http^0.218.0@opentelemetry/sdk-trace-node^2.7.1