Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

swagger-mock-validator

Package Overview
Dependencies
Maintainers
1
Versions
30
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

swagger-mock-validator - npm Package Versions

23

11.0.0

Diff

argos83
published 10.1.4 •

Changelog

Source

10.1.4 (2022-08-04)

Bug Fixes

  • replace unmaintained dependency request for axios (9fcd448)
argos83
published 10.1.3 •

Changelog

Source

10.1.3 (2022-03-15)

Bug Fixes

  • do not warn if mock expects content-type in HEAD response and no mime type are defined in the spec (b6aabbc), closes #75
argos83
published 10.1.2 •

Changelog

Source

10.1.2 (2022-01-10)

argos83
published 10.1.1 •

Changelog

Source

10.1.1 (2021-06-08)

Bug Fixes

  • properly validate formats in root array items (6213a82), closes #92
argos83
published 10.1.0 •

Changelog

Source

10.1.0 (2021-02-23)

Features

  • support Pact v3 query format (5bf15c3)
argos83
published 10.0.1 •

Changelog

Source

10.0.1 (2021-02-17)

Bug Fixes

  • accept header should match mime-types of any operation responses for openapi 3 (4f0eb55), closes #87
argos83
published 10.0.0 •

Changelog

Source

10.0.0 (2020-11-03)

Bug Fixes

  • fix bug when both nullable and swagger custom formats are defined (ed4acf9)

chore

BREAKING CHANGES

  • Dropped support for NodeJS v6 and v8. Migrate to NodeJS v10 or above.
medo-atlassian
published 9.0.0 •

Changelog

Source

9.0.0 (2019-11-07)

Bug Fixes

  • correctly validate request bodies containing a JSON null or false value (79fae8c)

Features

  • support the nullable attribute for data types (d3c13cc)

BREAKING CHANGES

  • Prior to this change the tool used to succeed when a pact request specified a request body containing solely the JSON literals ‘null' or 'false’, regardless of what the spec accepted. Now, request bodies with such values will only pass validation if the spec is okay with them.
argos83
published 8.0.0 •

Changelog

Source

8.0.0 (2019-09-18)

Bug Fixes

  • do not fail if an OpenApi 3 spec defines an empty security requirement (f42ceb1)

BREAKING CHANGES

  • Prior to this change the tool used to fail when a pact request with no auth was validated against an OpenApi 3 operation containing a security requirement (e.g. basic auth) plus an empty security requirement (which is normally used to represent that auth is optional). Now empty security requirements are considered for OpenApi3 specs hence not failing when the request lacks auth attributes.
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc