ata-validator
Ultra-fast JSON Schema validator. 5x faster validation, 159,000x faster compilation. Works without native addon. Cross-schema $ref, Draft 2020-12 + Draft 7, V8-optimized JS codegen, simdjson, RE2, multi-core. Standard Schema V1 compatible.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:node-api-headers | AI (phantom-deps): node-api-headers is a build-time dependency for native addons; not directly imported in JS but used by CMake/binding build. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in install.js to manage native binary loading; expected for native addon packages. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp-build is the standard prebuilt-binary loader for N-API addons; stable for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries are expected for a native N-API addon using prebuildify. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is used in the JS schema codegen path — standard pattern for schema validators like ajv. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is a build-time C++ header dep referenced in binding.gyp, not imported in JS. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.14.0 | 3 / 8 | |
| 0.13.3 | 3 / 7 | |
| 0.13.2 | 3 / 7 | |
| 0.12.3 | 3 / 7 | |
| 0.8.0 | 3 / 6 | |
| 0.6.0 | 2 / 7 | |
| 0.5.1 | 2 / 7 | |
| 0.4.15 | 2 / 5 |
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/ata-validator.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/ata-validator.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.15
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/ata-validator.node • prebuilds/linux-arm64/ata-validator.node • prebuilds/linux-x64/ata-validator.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.