swagger-api / swagger-api/swagger-codegen
Javascript client libraries are produced with 281 known vulnerabilities
Open
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Generating client libraries for Javascript creates JS code which npm reports as having:
281 vulnerabilities (279 low, 1 high, 1 critical)
Swagger-codegen version
3.0.20
Swagger declaration file content or url
https://developer.domain.com.au/docs/latest/media/v1/openapi.json
Command line used for generation
java -jar swagger-codegen-cli.jar generate -i https://developer.domain.com.au/docs/latest/media/v1/openapi.json -l javascript -o node-client
Steps to reproduce
- Run the swagger-codegen command
- Change to the
node-clientdirectory - Run
npm i
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the command in the issue with the linked OpenAPI document, then run npm i in the generated node-client directory and inspect the dependency report. Compare the generated package and its dependencies with the reported 281 vulnerabilities; done means the cause and an actionable correction to the generated JavaScript client are identified and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- security, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100