PkgRadar

Package evidence

[email protected]

no findings

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
15,816Mainstream · −50% score
Versions published
258
First published
May 2026
Publisher
sailwebs

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 monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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"}'
Publishersailwebs
Artifact bytes2,440,686
Previous version2.3.0-alpha.113
Published2026-06-17T12:19:20.448Z
SHA-256da49f99528038f57dc645f4a1cdfa1138502d1c233571e9b126291fd568aa322

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

low
Last checked
lowRisk
0Score
2.3.0-alpha.114Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts9
  • adminapi:buildyarn adminapi:bundle && sed "s/\"useDocker\": [a-z]*/\"useDocker\": ${USE_DOCKER:-true}/" ./src/adminapitools.json > ./openapitools.json && rm -rf ./src/adminapi && mkdir -p ./src/adminapi && openapi-generator-cli generate
  • adminapi:bundleredocly bundle ../apecloud/apiserver/api/adminapi.yaml > ./src/adminapi.yaml
  • api:buildyarn openapi:build && yarn adminapi:build && yarn internalapi:build
  • internalapi:buildyarn internalapi:bundle && sed "s/\"useDocker\": [a-z]*/\"useDocker\": ${USE_DOCKER:-true}/" ./src/internalapitools.json > ./openapitools.json && rm -rf ./src/internalapi && mkdir -p ./src/internalapi && openapi-generator-cli generate
  • internalapi:bundleredocly bundle ../apecloud/apiserver/api/internalapi.yaml > ./src/internalapi.yaml
  • openapi:buildyarn openapi:bundle && sed "s/\"useDocker\": [a-z]*/\"useDocker\": ${USE_DOCKER:-true}/" ./src/openapitools.json > ./openapitools.json && rm -rf ./src/openapi && mkdir -p ./src/openapi && openapi-generator-cli generate
  • openapi:bundleredocly bundle ../apecloud/apiserver/api/openapi.yaml > ./src/openapi.yaml
  • postapi:buildtsc
  • prepublishOnlyyarn api:build