PkgRadar

Package evidence

@kononenko-e/[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
204
Versions published
6
First published
May 2026
Publisher
kononenko-e

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":["@kononenko-e/[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":["@kononenko-e/[email protected]"],"fail_on":"review"}'
Publisherkononenko-e
Artifact bytes218,033
Previous version0.3.0
Published2026-06-01T08:53:58.243Z
SHA-2560528657aab7e380234eaf7986cd19e24be4199df8b588d8c8a7aa4c1b821908f

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

Scripts34
  • buildtsc -p tsconfig.build.json
  • changelogcog changelog
  • checkbiome check src/ && eslint src/
  • commitcog commit
  • devtsx watch src/main.ts
  • docker:builddocker build -t codefuturist/email-mcp .
  • docker:cleandocker images --format '{{.Repository}}:{{.Tag}}' | grep email-mcp | xargs docker rmi -f 2>/dev/null; true
  • docker:composedocker compose up
  • docker:prunedocker image prune -f && docker buildx prune -f
  • docker:rundocker run --rm -i -v ~/.config/email-mcp:/home/node/.config/email-mcp:ro codefuturist/email-mcp
  • formatbiome format --write src/
  • format:checkbiome check src/
  • hooks:installlefthook install --force
  • hooks:uninstalllefthook uninstall
  • linteslint src/
  • lint:fixeslint src/ --fix
  • preparelefthook install || true
  • prepublishOnlytsc -p tsconfig.build.json
  • release:checkgoreleaser check
  • release:dry-rungoreleaser release --skip=publish --clean && pnpm docker:clean
  • release:snapshotgoreleaser release --snapshot --clean && pnpm docker:clean
  • reportmkdir -p reports && biome check src/ --reporter=json > reports/biome.json 2>&1; eslint src/ -f json -o reports/eslint.json; actionlint -format '{{json .}}' > reports/actionlint.json 2>&1; pnpm test
  • startnode dist/main.js
  • testvitest run
  • test:allvitest run && vitest run --config vitest.config.integration.ts
  • test:coveragevitest run --coverage
  • test:integrationvitest run --config vitest.config.integration.ts
  • test:watchvitest
  • typechecktsc --noEmit
  • version:bumpcog bump --auto
  • …and 4 more.
Dependencies10
  • @clack/prompts^1.0.1
  • @modelcontextprotocol/sdk^1.26.0
  • @types/mime-types^3.0.1
  • imapflow^1.2.9
  • mailparser^3.9.9
  • mime-types^3.0.2
  • node-ical^0.25.2
  • nodemailer^8.0.1
  • smol-toml^1.6.0
  • zod^4.3.6