PkgRadar

Package evidence

@codingfactory/[email protected]

no findings

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":["@codingfactory/[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":["@codingfactory/[email protected]"],"fail_on":"review"}'
Publishercodingfactory
Artifact bytes298,916
Previous version1.0.18
Published2026-05-25T06:08:05.137Z
SHA-256311717e2319af55bc8c7ce6fb69d1914a2bff1e93a962ecdc93ecb2d7963768e

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.0.19Version
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

Scripts9
  • buildnpm run build:js && npm run build:types
  • build:jsvite build
  • build:typesvue-tsc -p tsconfig.build.json
  • checknpm run typecheck && npm run test && npm run build
  • prepublishOnlynpm run check
  • testvitest run
  • test:coveragevitest run --coverage
  • test:watchvitest
  • typecheckvue-tsc --noEmit