PkgRadar

Package evidence

[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.

Versions published
825Mature · −50% score
First published
Jun 2011
Publisher
dbx-node

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 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"}'
Publisherdbx-node
Artifact bytes572,649
Previous version4.17.1
Published2023-12-05T17:23:34.672Z
SHA-256c8dc719a35845c2b5563aded0771705d34ff350e6ddcaca3a727e1b63cd7d005

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
4.17.2Version
Status history (1 event)
  1. new → available · risk review · score 3 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/lib/cmap/auth/mongo_credentials.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/src/cmap/auth/mongo_credentials.tsmatched "AWS_ACCESS_KEY"5

Manifest

Package metadata

Scripts35
  • build:docs./etc/docs/build.ts
  • build:dtsnpm run build:ts && api-extractor run && node etc/clean_definition_files.cjs
  • build:evergreennode .evergreen/generate_evergreen_tasks.js
  • build:tsnode ./node_modules/typescript/bin/tsc
  • build:typedoctypedoc
  • check:adlmocha --config test/mocha_mongodb.json test/manual/atlas-data-lake-testing
  • check:atlasmocha --config test/manual/mocharc.json test/manual/atlas_connectivity.test.js
  • check:awsmocha --config test/mocha_mongodb.json test/integration/auth/mongodb_aws.test.ts
  • check:benchnode test/benchmarks/driverBench
  • check:coveragenyc npm run test:all
  • check:csflemocha --config test/mocha_mongodb.json test/integration/client-side-encryption
  • check:dependenciesmocha test/action/dependency.test.ts
  • check:dtsnode ./node_modules/typescript/bin/tsc --noEmit mongodb.d.ts && tsd
  • check:eslinteslint -v && eslint --max-warnings=0 --ext '.js,.ts' src test
  • check:integration-coveragenyc npm run check:test
  • check:kerberosmocha --config test/manual/mocharc.json test/manual/kerberos.test.js
  • check:lambdamocha --config test/mocha_lambda.json test/integration/node-specific/examples/handler.test.js
  • check:lambda:awsmocha --config test/mocha_lambda.json test/integration/node-specific/examples/aws_handler.test.js
  • check:ldapmocha --config test/manual/mocharc.json test/manual/ldap.test.js
  • check:lintnpm run build:dts && npm run check:dts && npm run check:eslint && npm run check:tsd
  • check:ocspmocha --config test/manual/mocharc.json test/manual/ocsp_support.test.js
  • check:snappymocha test/unit/assorted/snappy.test.js
  • check:socks5mocha --config test/manual/mocharc.json test/manual/socks5.test.ts
  • check:testmocha --config test/mocha_mongodb.json test/integration
  • check:tlsmocha --config test/manual/mocharc.json test/manual/tls_support.test.js
  • check:tsnode ./node_modules/typescript/bin/tsc -v && node ./node_modules/typescript/bin/tsc --noEmit
  • check:tsdtsd --version && tsd
  • check:unitmocha test/unit
  • fix:eslintnpm run check:eslint -- --fix
  • preparenode etc/prepare.js
  • …and 5 more.
Dependencies3
  • bson^4.7.2
  • mongodb-connection-string-url^2.6.0
  • socks^2.7.1
Optional dependencies2
  • @aws-sdk/credential-providers^3.186.0
  • @mongodb-js/saslprep^1.1.0