Package evidence

[email protected]

Credential file access: matched ".config/gcloud"

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: 26,416Mainstream · −50% score
Versions published: 420
First published: Feb 2026
Publisher: weiesky

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

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

Inspect tarball Add 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"}'

Publisherweiesky

Artifact bytes5,261,562

Previous version1.6.313

Published2026-06-17T05:46:38.995Z

SHA-2566c228258d931f2aadcaa0ecc79cba3dd16d6e9d6a6cd0329dc645168a84dbc69

Why flagged

What the scanner saw

Credential file access: matched ".config/gcloud"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review

13h agoLast checked

reviewRisk

7Score

1.6.314Version

Status history (2 events)

scan_error → available13h ago · risk review · score 7 · status scan_error -> available, risk none -> review, score none -> 7
new → scan_error13h ago · risk none · score — · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/cc-viewer/-/cc-viewer-1.6.314.tgz)

Evidence

Static findings

3 static · 0 from release diff · showing high-signal first.

No high-signal findings — see all findings below.

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
low	Credential file access	package/server/lib/im-deny.js	matched ".config/gcloud"	5
low	Credential file access	package/dist/assets/index-BOA52Ogr.js	matched "id_rsa"	5
low	Credential file access	package/server/pty-manager.js	matched ".ssh/"	5

Manifest

Package metadata

Scripts16

buildnode build.js
build:sourcemapCCV_SOURCEMAP=1 node build.js
devvite
electron:buildnpm run build && electron-builder
electron:check-sign./scripts/check-sign-config.sh
electron:develectron electron/main.js
electron:signnpm run electron:build && ./scripts/mac-sign.sh
lint:control-bytesnode scripts/check-no-control-bytes.js
prepublishOnlynpm run build
pretestnpm run lint:control-bytes
pretest:coveragenpm run lint:control-bytes
pretest:coverage:htmlnpm run lint:control-bytes
startnode server.js
testCCV_LOG_DIR=tmp CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 node --test --test-force-exit --test-timeout=120000
test:coverageCCV_LOG_DIR=tmp CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 node --test --test-force-exit --test-timeout=120000 --experimental-test-coverage --test-coverage-include='server/**/*.js' --test-coverage-include='src/utils/**/*.js' --test-coverage-include='*.js'
test:coverage:htmlCCV_LOG_DIR=tmp CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 c8 --reporter=text-summary --reporter=html node --test --test-force-exit --test-timeout=120000

Dependencies9

@larksuiteoapi/node-sdk1.66.0
@wecom/aibot-node-sdk1.0.7
adm-zip^0.5.17
dingtalk-stream2.1.5
discord.js14.26.4
dompurify^3.3.3
node-pty^1.1.0
undici^7.22.0
ws^8.21.0

Optional dependencies1

@anthropic-ai/claude-agent-sdk^0.2.91