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 promotingMixed 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"}'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
Status history (1 event)
- new → available · risk review · score 30 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Credential file access | package/server/index.js | matched "AWS_ACCESS_KEY" | 30 |
Manifest
Package metadata
Scripts17
####### Build ############## Dependencies ############## Example ############## Linting ############## Server #######builddocker build -f "./Dockerfile" .check:deps:interactivenpm-check -uexample:builddocker-compose -p spa-static-example -f examples/example.yml buildexample:downdocker-compose -p spa-static-example -f examples/example.yml downexample:remote:builddocker-compose -p spa-static-example-remote -f examples/example-remote.yml buildexample:remote:downdocker-compose -p spa-static-example-remote -f examples/example-remote.yml downexample:remote:updocker-compose -p spa-static-example-remote -f examples/example-remote.yml upexample:updocker-compose -p spa-static-example -f examples/example.yml uplinteslint .pubnpm run build && docker --config ~/.docker-docker push transcendio/spa-static-server:lateststartBUILD_ENV_PATH=./examples/example.env node serverstart:cliBUILD_ENV_PATH=./examples/example.env ./cli.js
Dependencies10
chalk^2.4.2compression^1.7.4dotenv^8.0.0express^4.17.1http-proxy-middleware^0.20.0https^1.0.0node-fetch^2.6.0webpack^4.35.0webpack-dev-middleware^3.7.0webpack-hot-middleware^2.25.0