← Home

@sourceregistry/node-validator

npm Repository Homepage

A minimal, dependency-free TypeScript/JavaScript library for runtime validation.

8
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

alexander2000

Keywords

validationvalidatorschemaruntime-validationtypescriptzero-dependency

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.pattern:validator AI (typosquat): Scoped package under @sourceregistry with matching GitHub org; name similarity is incidental, not impersonation. ai

Versions (showing 8 of 8)

Version Deps Published
1.2.1 0 / 13
1.1.6 0 / 13
1.1.5 0 / 13
1.1.4 0 / 13
1.1.3 0 / 13
1.1.2 0 / 13
1.1.1 0 / 12
1.0.0 0 / 12

v1.2.1

2 findings
HIGH typosquat.pattern: Suspicious name similarity to 'validator' typosquat

Package name '@sourceregistry/node-validator' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'validator'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.