PkgRadar

Package evidence

@targetprocess/[email protected]

no findings

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
540Mature · −50% score
First published
Jun 2019
Publisher
targetprocess-user

Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

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":["@targetprocess/[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":["@targetprocess/[email protected]"],"fail_on":"review"}'
Publishertargetprocess-user
Artifact bytes15,177
Previous version1.30.6
Published2026-02-11T08:54:13.084Z
SHA-2564a86d5a98f8a790e00cb34b59e5ba35940719bab85cd98f108af33e0650327d1

Why flagged

What the scanner saw

No high-signal static finding in the saved report.

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

Availability ledger

available

low
Last checked
lowRisk
0Score
1.31.0Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts4
  • buildtsc --pretty
  • build:clientnpm run client:generate && npm run build
  • client:generatenpm run client:generate:ts
  • client:generate:tsnswag swagger2tsclient /ClassName:Client /Template:Fetch /PromiseType:Promise /DateTimeType:Date /GenerateClientInterfaces:true /GenerateConstructorInterface:true /GenerateDefaultValues:true /Input:api/swagger.yaml /Output:src/client/src/client.ts /TypeStyle:Interface /TypeScriptVersion:2.5 /WrapDtoExceptions:false /ExtendedClasses: /ExtensionCode: