kriszyp/json-schema

Issues

• json-schema is vulnerable to Prototype Pollution

  #90 opened a year ago by NicestRudeGuy
  2

• security bug

  #88 opened 3 years ago by surayp
  4

• New release tag

  #85 opened 3 years ago by jschirrmacher
  1

• This repos description should note the official repo location

  #54 opened 3 years ago by Relequestual
  0

• Create SECURITY.md

  #84 opened 3 years ago by zidingz
  1

• please tag releases

  #83 opened 3 years ago by jonassmedegaard
  2

• Is this project abandoned?

  #76 opened 4 years ago by jb-reefer
  5

• BSD License Clause

  #69 opened 5 years ago by subashthirumaran
  3

• lib/links.js and lib/validate.js are MIT licensed but package.json states BSD or AFL

  #62 opened 5 years ago by piotr1212
  1

• Reduce the size of the npm package by limiting the included files

  #79 opened 5 years ago by paazmaya
  2

• npm install broken: Cannot find module 'json-schema'

  #29 opened 13 years ago by timoxley
  4

• Json.Net 9.0 reference

  #74 opened 7 years ago by AlessandroP8
  0

• Where can I find examples of usage in javascript code?

  #22 opened 13 years ago by dhruvbird
  3

• Incompatible with webpack

  #59 opened 8 years ago by morgante
  12

• blarg - wrong input box!

  #65 opened 9 years ago by tmpvar
  0

• "format" property on the meta-schema

  #60 opened 9 years ago by heruan
  0

• Citing JSON-schema

  #58 opened 9 years ago by shachibista
  1

• Why is `links` an array and not an object?

  #51 opened 9 years ago by Kosta-Github
  1

• Implement RFC 6570

  #56 opened 10 years ago by wshager
  1

• Cannot self validate meta schema

  #55 opened 10 years ago by vicary
  0

• null is allowed as a valid object

  #46 opened 10 years ago by davepacheco
  1

• Extension to allow non-JSON JavaScript

  #53 opened 10 years ago by brettz9
  0

• Update json-schema.org A record

  #52 opened 10 years ago by mchelen
  2

• Code?

  #50 opened 10 years ago by L2L2L
  0

• validate shouldn't mutate input

  #37 opened 11 years ago by jfirebaugh
  1

• "date-time" format is not validated

  #48 opened 10 years ago by davepacheco
  0

• strings are allowed as numbers

  #47 opened 10 years ago by davepacheco
  0

• draft 4 schema doesn't require

  #38 opened 11 years ago by jdarling
  8

• Use coerce and object/string

  #44 opened 11 years ago by kostyak76
  0

• Incorrect Object validation

  #42 opened 11 years ago
  0

• Only validates by draft 3 rules

  #41 opened 11 years ago by murgatroid99
  0

• Handle the issues and update NPM

  #40 opened 11 years ago by Bartvds
  0

• date-time format value doesn't work

  #36 opened 12 years ago by vlamic
  1

• property name lost in validation message

  #39 opened 11 years ago by bubenshchykov
  0

• Why this example of referencing schema inside same object does not work?

  #35 opened 12 years ago
  0

• Arrays and Dates validate as objects

  #30 opened 13 years ago by timoxley
  2

• uniqueItems is not validated

  #34 opened 12 years ago by krisnye
  0

• published version 0.2.1 in npm registry has the wrong version in its package.json

  #33 opened 12 years ago by c4milo
  0

• null validates as a valid integer

  #23 opened 13 years ago by neonstalwart
  0

• publish to npm

  #21 opened 13 years ago by tmpvar
  3

• validate.js is unable to validate core schema

  #17 opened 14 years ago by laurie71
  6

• looks like validate does not do anything

  #20 opened 13 years ago by markfink
  2

• 'required' property is not supported, but obsolete 'optional' is

  #16 opened 13 years ago by laurie71
  2

• coerce

  #13 opened 14 years ago by dvv
  2

• messages

  #12 opened 14 years ago by dvv
  1

• underscored specialty?

  #11 opened 14 years ago by dvv
  2

• exports.coerce

  #10 opened 14 years ago by dvv
  2