PkgRadar

Package evidence

@theoptimalpartner/[email protected]

Credential file access: matched "AWS_ACCESS_KEY"

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
35
Versions published
19Established · −30% score
First published
Jun 2025
Publisher
theoptimalpartner

Effective trust discount applied: −30% (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 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":["@theoptimalpartner/[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":["@theoptimalpartner/[email protected]"],"fail_on":"review"}'
Publishertheoptimalpartner
Artifact bytes42,103
Previous version2.1.0-beta.1
Published2025-11-20T19:23:51.753Z
SHA-2567e565434e1c4ad68a1651545c00745ca143f4057ac506403edf0662b0ab46138

Why flagged

What the scanner saw

Credential file access: matched "AWS_ACCESS_KEY"

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

Availability ledger

available

review
Last checked
reviewRisk
3Score
2.1.0Version
Status history (1 event)
  1. new → available · risk review · score 3 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 1 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/dist/ssm-service.jsmatched "AWS_ACCESS_KEY"5

Manifest

Package metadata

Scripts19
  • buildtsc
  • cleanrm -rf dist
  • devtsc --watch
  • linteslint src/**/*.ts
  • lint:fixeslint src/**/*.ts --fix
  • preparehusky install
  • prepublishOnlynpm run build
  • security:auditnpm audit --audit-level=moderate
  • security:audit:fixnpm audit fix
  • security:check./scripts/security-check.sh
  • security:check-malicious./scripts/check-malicious-packages.sh
  • security:fullnpm run security:audit && npm run security:check
  • security:integrate-pipelinebash ./node_modules/@theoptimalpartner/npm-security-kit/bin/integrate-pipeline.sh || bash $(npm root -g)/@theoptimalpartner/npm-security-kit/bin/integrate-pipeline.sh 2>/dev/null || echo "Run: npx @theoptimalpartner/npm-security-kit integrate-pipeline"
  • security:licensesnpm list --json | jq -r '.dependencies | to_entries[] | "\(.key): \(.value.license)"'
  • security:outdatednpm outdated
  • security:setup-huskybash ./node_modules/@theoptimalpartner/npm-security-kit/bin/setup-husky.sh || bash $(npm root -g)/@theoptimalpartner/npm-security-kit/bin/setup-husky.sh 2>/dev/null || echo "Run: npx @theoptimalpartner/npm-security-kit setup-husky"
  • testjest
  • test:coveragejest --coverage
  • test:watchjest --watch
Dependencies5
  • @aws-sdk/client-ssm^3.883.0
  • crypto-browserify^3.12.1
  • ioredis^5.6.1
  • jose^6.1.0
  • node-cache^5.1.2