PkgRadar

Package evidence

@communecter/[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
565
Versions published
133Mature · −50% score
First published
Apr 2025
Publisher
aboire

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":["@communecter/[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":["@communecter/[email protected]"],"fail_on":"review"}'
Publisheraboire
Artifact bytes760,933
Previous version1.0.134
Published2026-05-26T09:45:06.942Z
SHA-25604c7ce380f7b54db57b200358e7c9e63d46010b725a08e6f98f04250278eb73c

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
1.0.135Version
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

Scripts23
  • buildnpm run generate:module:publish && npm run generate:methodeapi && npm run generate:doc && npm run lint:fix && npm run build:browser && npm run build:node && npm run build:esm && npm run build:esm:rollup && npm run build:types
  • build:browserwebpack --config webpack.config.standalone.js
  • build:esmwebpack --config webpack.config.esm.mjs
  • build:esm:rolluprollup -c rollup.config.mjs
  • build:nodewebpack --config webpack.config.node.js
  • build:publishnpm run build && npm publish --access public
  • build:tstsc --project tsconfig.json
  • build:typesnpm run generate:methodeapi && tsc --project tsconfig.types.json
  • exemplenode exemple/exemple.js
  • exemple-apitsx exemple/exemple-api.ts
  • generate:docnode ./scripts/generate-doc.js
  • generate:methodeapinode ./scripts/generate-methode-api.js
  • generate:modulenode ./scripts/transform-json-module.js
  • generate:module:publishnode ./scripts/transform-json-module.publish.js
  • generate:reponsesnode ./scripts/generate-constant-response-200.js
  • linteslint ./src ./scripts --ext .js,.ts
  • lint:fixeslint ./src ./scripts --ext .js,.ts --fix
  • testvitest run
  • test:oldnode --experimental-vm-modules ./node_modules/.bin/jest --config jest.config.js
  • test:uivitest --ui
  • test:watchvitest watch
  • typechecktsc --noEmit
  • verif:esmwebpack --config webpack.config.esm.mjs --profile --json > stats.json