Package evidence

@swagger-api/[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.

Weekly downloads: 584,723Ubiquitous · −70% score
Versions published: 10
First published: Feb 2026
Publisher: swagger-api

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

Looks clean — keep monitoring

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

Inspect tarball Add 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":["@swagger-api/[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":["@swagger-api/[email protected]"],"fail_on":"review"}'

Publisherswagger-api

Artifact bytes392,491

Previous version1.11.0

Published2026-05-12T08:34:35.716Z

SHA-2564851b7d79d07f5bb40f57a392acc085f6b4de44d8bbd058ab83285c52f3e8340

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

15d agoLast checked

lowRisk

0Score

1.11.1Version

Status history (1 event)

new → available15d ago · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts17

buildnpm run clean && run-p --max-parallel ${CPU_CORES:-6} typescript:declaration build:es build:cjs build:umd:browser
build:cjscross-env BABEL_ENV=cjs babel src --out-dir src --extensions '.ts' --out-file-extension '.cjs' --root-mode 'upward'
build:escross-env BABEL_ENV=es babel src --out-dir src --extensions '.ts' --out-file-extension '.mjs' --root-mode 'upward'
build:umd:browservite build
cleanrimraf --glob 'src/**/*.mjs' 'src/**/*.cjs' ./dist ./types
linteslint ./
lint:fixeslint ./ --fix
perfcross-env BABEL_ENV=es babel ./test/perf/index.ts --out-file ./test/perf/index.mjs --root-mode 'upward' && cross-env NODE_ENV=test node ./test/perf/index.mjs
perf:lexical-analysiscross-env BABEL_ENV=es babel ./test/perf/lexical-analysis.ts --out-file ./test/perf/lexical-analysis.mjs --root-mode 'upward' && cross-env NODE_ENV=test node ./test/perf/lexical-analysis.mjs
perf:parsecross-env BABEL_ENV=es babel ./test/perf/parse.ts --out-file ./test/perf/parse.mjs --root-mode 'upward' && cross-env NODE_ENV=test node ./test/perf/parse.mjs
perf:refractcross-env BABEL_ENV=es babel ./test/perf/refract.ts --out-file ./test/perf/refract.mjs --root-mode 'upward' && cross-env NODE_ENV=test node ./test/perf/refract.mjs
perf:syntactic-analysiscross-env BABEL_ENV=es babel ./test/perf/syntactic-analysis.ts --out-file ./test/perf/syntactic-analysis.mjs --root-mode 'upward' && cross-env NODE_ENV=test node ./test/perf/syntactic-analysis.mjs
postpackrimraf NOTICE LICENSES
prepackcopyfiles -u 3 ../../LICENSES/* LICENSES && copyfiles -u 2 ../../NOTICE .
testNODE_ENV=test ts-mocha --exit
typescript:check-typestsc --noEmit && tsc -p ./test/tsconfig.json --noEmit
typescript:declarationtsc -p tsconfig.declaration.json && api-extractor run -l -c ./config/api-extractor/api-extractor.json

Dependencies7

@babel/runtime-corejs3^7.26.10
@swagger-api/apidom-core^1.11.1
@swagger-api/apidom-ns-openapi-3-2^1.11.1
@swagger-api/apidom-parser-adapter-yaml-1-2^1.11.1
@types/ramda~0.30.0
ramda~0.30.0
ramda-adjunct^5.0.0