PkgRadar

Package evidence

@edifice.io/[email protected]

Credential file access: matched ".npmrc"

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
310Established · −30% score
First published
Jun 2025
Publisher
wsejenkins

Effective trust discount applied: −30% (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":["@edifice.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":["@edifice.io/[email protected]"],"fail_on":"review"}'
Publisherwsejenkins
Artifact bytes81,447
Previous version1.4.3-develop.1.20260603153547
Published2026-06-03T15:49:58.042Z
SHA-256d7c9b0ff36d0d55dd93f2feffddef053ff3b2b870b74e68760aad50bf6b92a77

Why flagged

What the scanner saw

Credential file access: matched ".npmrc"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review
Last checked
reviewRisk
2Score
1.4.3-develop.1.20260603154950Version
Status history (1 event)
  1. new → available · risk review · score 2 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 1 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/package.jsonmatched ".npmrc"3

Manifest

Package metadata

Scripts19
  • buildpnpm run build:node && pnpm run build:browser && pnpm run build:react-native
  • build:browsertsc -p tsconfig.browser.json --outDir dist/browser && rest-client-base replace --module browser
  • build:nodetsc -p tsconfig.node.json --outDir dist/node && tsc -p tsconfig.node.json --outDir dist/node
  • build:prodNODE_ENV=production pnpm run build:node && pnpm run build:browser && pnpm run build:react-native
  • build:react-nativetsc -p tsconfig.browser.json --outDir dist/react-native && rest-client-base replace --module react-native
  • cleanrm -rf dist node_modules
  • formatprettier --write src
  • linteslint src
  • lint:fixeslint src --fix
  • prebuildpnpm clean && pnpm install
  • prune:prodCI=true NPM_CONFIG_IGNORE_SCRIPTS=true pnpm prune --prod --production --loglevel verbose
  • publish:allpnpm run publish:main && pnpm run publish:react-native
  • publish:mainpnpm run sync:rn-version && npm publish --no-git-checks --access public --tag=$PUBLISH_TAG --dry-run=${DRY_RUN}
  • publish:react-nativepnpm run sync:rn-version && cp package.json.rn dist/react-native/package.json && cp .npmrc dist/react-native/ && cd dist/react-native && npm publish --no-git-checks --access public --tag=$PUBLISH_TAG --dry-run=${DRY_RUN}
  • sync:rn-versionedifice-update-rn-version
  • testpnpm run prebuild && vitest
  • test:coveragevitest --coverage
  • test:uivitest --ui
  • test:watchvitest --watch
Dependencies2
  • @edifice.io/rest-client-basedevelop
  • @nestjs/swagger11.2.0