swagger2-to-postmanv2

v2.1.0

A module to convert swagger 2.0 specs to Postman Collection Format v2 For more information about how to use this package see README

Latest version published 2 years ago

License: Apache-2.0

NPM

GitHub

Package Health Score

45 / 100

security
Security review needed
popularity
Small
maintenance
Inactive
community
Limited

Explore Similar Packages

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
2.1.0	\|	03/2022	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.0.1	\|	03/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.0.3	\|	09/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.2.0	\|	11/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.1.0	\|	10/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

Apache-2.0

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Small

Weekly Downloads (1,103)

GitHub Stars: 79
Forks: 42
Contributors: -

Direct Usage Popularity

The npm package swagger2-to-postmanv2 receives a total of 1,103 downloads a week. As such, we scored swagger2-to-postmanv2 popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package swagger2-to-postmanv2, we found that it has been starred 79 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 0
Funding: No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like swagger2-to-postmanv2 is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 12
Open PR: 17
Last Release: 2 years ago
Last Commit: 2 years ago

Further analysis of the maintenance status of swagger2-to-postmanv2 based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for swagger2-to-postmanv2 is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=8

Age: 5 years
Dependencies: 4 Direct
Versions: 13
Install Size: 34.8 kB
Dist-tags: 1
# of Files: 12
Maintainers: 4
TS Typings: No

swagger2-to-postmanv2 has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

swagger2-Postman

Converter for swagger 2.0 JSON to Postman Collection v2 Exports the following functions:

validate(JSON-or-string)*: Formats like RAML/cURL don't have a JSON representation. For others, JSON is preferred. The result should be an object: {result: true/false, reason: 'string'}. Reason must be populated if the result is false. This function will be used by the app to determine whether or not this converter can be used for the given input.
convert(JSON-or-string)*: Converts the input to a collection object. Conversion result should be an object: {result: true/false, reason: '', output:[{type: 'collection', data: }] Reason must be populated if the result is false. Collection must be populated if result is true.

Conversion Schema

Postman	Swagger2	options	examples
collectionName	info.title	-	-
description	info.description	-	-
folderName	paths.path	-	-
requestName	method.summary \|\| method.operationId \|\| request.url.raw(in postman)	default('operationId') -(`requestName`) enum[['operationId','summary','url']	-
request.method	path.method (`all possible http methods`)	-	-
request.headers	params (`in = header` )	-	here
request.body	params (`in = body or formBody`)	default(true)-(`schemaFaker`)use json-schema-faker for body conversion	here
request.url.raw	scheme(http or https) + '😕/' + host + basePath	-	-
request.url.params	params (`in = query`)	-	here
request.url.variables	params (`in = path`)	-	here
Content-Type header	consumes	default(true) - add consumes to header	-
Accept header	produces	default(true) - add produces to header	-
apikey in (query or header)	securityDefinitions(`type = apiKey`)	-	-

Header/Query/Path param conversion example

swagger	postman
name: api-key description: session token in: header type: integer default: defaultValue	{ "key": "api-key", "value": defaultValue, "description": "session token" }

Body param conversion example

If `in = body`

swagger	postman
name: role-id description: role identifier number in: body schema: \|"body": { "mode": "raw", "raw": json-schema-faker() }

If `in = formData` and `consumes = application/x-www-form-urlencoded`

swagger	postman
name: role-id description: role identifier number in: formData default: defaultValue	"body": { "mode": "urlencoded", "urlencoded": [{ "key": "role-id", "value": defaultValue, "type": "text", }] }
> All parmas with above condition are added to urlencoded array.

If `in = formData` and `consumes = multipart/form-data`

swagger	postman
name: role-id description: role identifier number in: formData default: defaultValue	"body": { "mode": "formdata", "formdata": [{ "key": "role-id", "value": defaultValue, "type": "text", }] }
> All parmas with above condition are added to formdata array.

swagger2-to-postmanv2 dependencies

js-yaml lodash openapi-to-postmanv2 swagger2openapi

swagger2-to-postmanv2 development dependencies

chai eslint eslint-plugin-security istanbul mocha nsp

FAQs

What is swagger2-to-postmanv2?

A module to convert swagger 2.0 specs to Postman Collection Format v2. Visit Snyk Advisor to see a full health score report for swagger2-to-postmanv2, including popularity, security, maintenance & community analysis.

Is swagger2-to-postmanv2 popular?

The npm package swagger2-to-postmanv2 receives a total of 1,103 weekly downloads. As such, swagger2-to-postmanv2 popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is swagger2-to-postmanv2 well maintained?

We found indications that swagger2-to-postmanv2 is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is swagger2-to-postmanv2 safe to use?

While scanning the latest version of swagger2-to-postmanv2, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 9 April-2024, at 19:07 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP