PkgRadar

Package evidence

@transcend-io/[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
5
Versions published
9
First published
Jun 2019
Publisher
michaelfarrell76

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":["@transcend-io/[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":["@transcend-io/[email protected]"],"fail_on":"review"}'
Artifact bytes8,875
Previous version1.0.7
Published2019-09-22T01:54:22.688Z
SHA-2561464dd04e34ae5a96cfb8996c9e58c888cbdc5480fb7047c246a8c8ccca5c4b1

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

Evidence

Static findings

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

SeverityKindPathDetailPoints
highCredential file accesspackage/server/index.jsmatched "AWS_ACCESS_KEY"30

Manifest

Package metadata

Scripts17
  • ####### Build #######
  • ####### Dependencies #######
  • ####### Example #######
  • ####### Linting #######
  • ####### Server #######
  • builddocker build -f "./Dockerfile" .
  • check:deps:interactivenpm-check -u
  • example:builddocker-compose -p spa-static-example -f examples/example.yml build
  • example:downdocker-compose -p spa-static-example -f examples/example.yml down
  • example:remote:builddocker-compose -p spa-static-example-remote -f examples/example-remote.yml build
  • example:remote:downdocker-compose -p spa-static-example-remote -f examples/example-remote.yml down
  • example:remote:updocker-compose -p spa-static-example-remote -f examples/example-remote.yml up
  • example:updocker-compose -p spa-static-example -f examples/example.yml up
  • linteslint .
  • pubnpm run build && docker --config ~/.docker-docker push transcendio/spa-static-server:latest
  • startBUILD_ENV_PATH=./examples/example.env node server
  • start:cliBUILD_ENV_PATH=./examples/example.env ./cli.js
Dependencies10
  • chalk^2.4.2
  • compression^1.7.4
  • dotenv^8.0.0
  • express^4.17.1
  • http-proxy-middleware^0.20.0
  • https^1.0.0
  • node-fetch^2.6.0
  • webpack^4.35.0
  • webpack-dev-middleware^3.7.0
  • webpack-hot-middleware^2.25.0