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
245Mature · −50% score
First published
May 2025
Publisher
pyramation

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.

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"}'
Publisherpyramation
Artifact bytes61,581
Previous version5.7.1
Published2026-06-17T07:35:29.602Z
SHA-2566ada8cde5b342ff8653fb06f87e08f800225a11e0bfd283cf215944b9c22a547

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
10Score
5.8.0Version
Status history (1 event)
  1. newavailable · risk review · score 10 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 4 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/bucket-provisioner-resolver.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/esm/bucket-provisioner-resolver.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/esm/presigned-url-resolver.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/presigned-url-resolver.jsmatched "AWS_ACCESS_KEY"5

Manifest

Package metadata

Scripts7
  • buildmakage build
  • build:devmakage build --dev
  • cleanmakage clean
  • linteslint . --fix
  • prepacknpm run build
  • testjest
  • test:watchjest --watch
Dependencies42
  • @aws-sdk/client-s3^3.1052.0
  • @constructive-io/bucket-provisioner^0.12.0
  • @constructive-io/graphql-env^3.13.0
  • @constructive-io/graphql-types^3.12.0
  • @constructive-io/s3-streamer^2.26.0
  • @constructive-io/s3-utils^2.18.0
  • @constructive-io/upload-names^2.17.0
  • @dataplan/json1.0.0
  • @dataplan/pg1.0.3
  • @graphile-contrib/pg-many-to-many2.0.0-rc.2
  • @pgpmjs/logger^2.12.0
  • @pgpmjs/types^2.29.0
  • @pgsql/quotes^17.1.0
  • cors^2.8.6
  • express^5.2.1
  • grafast1.0.2
  • grafserv1.0.0
  • graphile-bucket-provisioner-plugin0.12.0
  • graphile-build5.0.2
  • graphile-build-pg5.0.2
  • graphile-bulk-mutations^0.5.4
  • graphile-config1.0.1
  • graphile-connection-filter^1.12.4
  • graphile-i18n^1.2.5
  • graphile-llm^0.12.1
  • graphile-ltree^1.9.5
  • graphile-pg-aggregates^1.5.4
  • graphile-postgis^2.18.4
  • graphile-presigned-url-plugin^0.20.0
  • graphile-realtime-subscriptions^0.8.1
  • …and 12 more.