PkgRadar

Package evidence

@interopio/[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
87Established · −30% score
First published
Sep 2025
Publisher
GitHub ActionsTrusted automation · −70% score

Effective trust discount applied: 70% (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":["@interopio/[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":["@interopio/[email protected]"],"fail_on":"review"}'
Artifact bytes2,246,642
Previous version0.0.88
Published2026-06-03T09:33:24.073Z
SHA-2564cae9b9bd8c6b01647c841595902ee5a1a578b59e80d068e7a5b2336a1b40aad

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

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 5 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/dist/services/config/config.service.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/services/components/stores/s3.store.jsmatched "AWS_ACCESS_KEY"5
lowInstall-time lifecycle scriptpackage.jsonpostinstall="npm run gitignore:post-install"5
lowCredential file accesspackage/dist/schemas/iocd.cli.config.schema.jsonmatched "AWS_ACCESS_KEY"3
lowObfuscation Densitypackage/dist/templates/launchpad/apps/launchpad/package-lock.jsonhigh encoded/escaped-token density0

Manifest

Package metadata

Scripts17
  • buildnode ./scripts/delete-dist.js && tsc && npm run format && npm run lint && npm run generate-schema && npm run copy-assets
  • clinpm run build && node dist/cli.js
  • copy-assetsnode ./scripts/copy-assets.js
  • devtsc --watch
  • formatprettier --write src/**/*.ts*
  • generate-schemanode ./scripts/generate-schema.js
  • gitignore:post-installnode ./scripts/handle-gitignore-templates.js post-install
  • gitignore:post-publishnode ./scripts/handle-gitignore-templates.js post-publish
  • gitignore:pre-packagenode ./scripts/handle-gitignore-templates.js pre-package
  • linteslint src --ext .ts
  • lint:fixeslint src --ext .ts --fix
  • postinstallnpm run gitignore:post-install
  • postpublishnpm run gitignore:post-publish
  • preparehusky
  • prepublishOnlynpm run build && npm run gitignore:pre-package
  • testcross-env NODE_OPTIONS=--no-experimental-webstorage jest
  • test:watchcross-env NODE_OPTIONS=--no-experimental-webstorage jest --watch
Dependencies13
  • @clack/prompts^0.7.0
  • @electron/notarize^3.1.0
  • @electron/osx-sign^2.2.0
  • @sentry/node^10.17.0
  • adm-zip^0.5.17
  • commander^14.0.0
  • concurrently^9.2.1
  • dotenv^17.2.2
  • fs-extra^11.3.1
  • jsonwebtoken^9.0.2
  • log4js^6.9.1
  • plist^3.1.0
  • undici^7.16.0