Package evidence
@openfort/[email protected]
Install-time lifecycle script: preinstall="npx only-allow pnpm"
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
- 3,597Niche · −30% score
- Versions published
- 139Mature · −50% score
- First published
- May 2023
- 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
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
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":["@openfort/[email protected]"],"fail_on":"high"}'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":["@openfort/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: preinstall added in 0.10.4 vs 0.10.3: "npx only-allow pnpm"
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 high · score 45 · status changed
Evidence
Static findings
1 static · 1 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | preinstall added in 0.10.4 vs 0.10.3: "npx only-allow pnpm" | 40 |
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | preinstall added in 0.10.4 vs 0.10.3: "npx only-allow pnpm" | 40 |
| low | Install-time lifecycle script | package.json | preinstall="npx only-allow pnpm" | 5 |
Manifest
Package metadata
Scripts19
buildtsupchangesetchangesetchangeset:prepublishpnpm buildchangeset:publishpnpm build && changeset publishchangeset:versionpnpm install --lockfile-only && changeset versioncheckbiome check --write --unsafecheck:exportsattw --pack . --ignore-rules false-esmcheck:typestsc --noEmitdocstypedoc --entryPoints src/index.ts --out docs/ --includes src/**/*.tsdocs:jsontypedoc --entryPoints src/index.ts --includes src/**/*.ts --json docs/spec.json --excludeExternalslintbiome lintorvalmake check-openapi || echo 'NOTE: A newer OpenAPI spec is available. Run pnpm orval:update to update.'; orval --config orval.config.tsorval:updatemake update-openapi && orval --config orval.config.tsprebuildnode -p "'export const VERSION = \'' + require('./package.json').version + '\'\nexport const PACKAGE = \'' + require('./package.json').name + '\''" > src/version.tspreinstallnpx only-allow pnpmtestvitest runtest:buildpublint --strict && attw --pack . --ignore-rules false-esmtest:civitest run --reporter=verbosetest:covvitest run --coverage
Dependencies6
@openfort/shield-js^0.1.36axios^1.15.0axios-retry^4.5.0bs58^6.0.0jose^6.2.1zod^3.25.76