
Security News
Open VSX Unblocks Extension IDs Used in Malware Campaign
Open VSX has removed three extension IDs from its malicious-extension list as the legitimate publishers they impersonated move to claim the names for themselves.
@apideck/better-ajv-errors
Advanced tools
Human-friendly JSON Schema validation for APIs

$ yarn add @apideck/better-ajv-errors
or
$ npm i @apideck/better-ajv-errors
Also make sure that you've installed ajv at version 8 or higher.
After validating some data with ajv, pass the errors to betterAjvErrors
import Ajv from 'ajv';
import { betterAjvErrors } from '@apideck/better-ajv-errors';
// Without allErrors: true, ajv will only return the first error
const ajv = new Ajv({ allErrors: true });
const valid = ajv.validate(schema, data);
if (!valid) {
const betterErrors = betterAjvErrors({ schema, data, errors: ajv.errors });
}
Function that formats ajv validation errors in a human-friendly format.
options: BetterAjvErrorsOptions
errors: ErrorObject[] | null | undefined Your ajv errors, you will find these in the errors property of your ajv instance (ErrorObject is a type from the ajv package).data: Object The data you passed to ajv to be validated.schema: JSONSchema The schema you passed to ajv to validate against.basePath?: string An optional base path to prefix paths returned by betterAjvErrors. For example, in APIs, it could be useful to use '{requestBody}' or '{queryParemeters}' as a basePath. This will make it clear to users where exactly the error occurred.ValidationError[] Array of formatted errors (properties of ValidationError below)
message: string Formatted error messagesuggestion?: string Optional suggestion based on provided data and schemapath: string Object path where the error occurred (example: .foo.bar.0.quz)context: { errorType: DefinedError['keyword']; [additionalContext: string]: unknown } errorType is error.keyword proxied from ajv. errorType can be used as a key for i18n if needed. There might be additional properties on context, based on the type of error.ajv-errors is a package that allows custom error messages in Ajv. It provides a way to define custom error messages for specific validation keywords, offering more control over the error output. Unlike @apideck/better-ajv-errors, which focuses on making default error messages more readable, ajv-errors allows for custom error message definitions.
ajv-i18n is a package that provides internationalization (i18n) support for Ajv error messages. It translates Ajv error messages into different languages. While @apideck/better-ajv-errors focuses on making error messages more human-readable in English, ajv-i18n is useful for applications that need to support multiple languages.
FAQs
Human-friendly JSON Schema validation for APIs
The npm package @apideck/better-ajv-errors receives a total of 6,828,297 weekly downloads. As such, @apideck/better-ajv-errors popularity was classified as popular.
We found that @apideck/better-ajv-errors demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 7 open source maintainers collaborating on the project.

Security News
Open VSX has removed three extension IDs from its malicious-extension list as the legitimate publishers they impersonated move to claim the names for themselves.

Product
Socket’s PHP and Composer support is now in Beta for all customers, with PHP reachability analysis generally available.

Product
Socket is bringing experimental protection to Firefox, scanning 97,000+ extensions in Mozilla's official directory for malware and risky updates.