← Home

@encatch/schema

npm Homepage
9
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

siddhesh.shirdhankargodwin.pinto

Keywords

zodtypescriptschemavalidationtypes

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Publisher has strong track record; likely a one-off manual publish rather than a supply chain concern. ai
phantom-deps phantom-dep:uuid AI (phantom-deps): uuid is a declared runtime dependency; phantom-dep heuristic is a false positive. ai
phantom-deps phantom-dep:typescript AI (phantom-deps): typescript is a declared runtime dependency; phantom-dep heuristic is a false positive. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): Framework-scoped type package; phantom-dep heuristic is a false positive. ai

Versions (showing 9 of 9)

Version Deps Published
1.2.0 3 / 4
1.1.1 3 / 6
1.1.0 3 / 6
0.1.37 3 / 6
0.1.36 3 / 6
0.1.35 3 / 6
0.1.34 3 / 6
0.1.33 3 / 6
0.1.32 3 / 6

v1.2.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: godwin.pinto.

LOW No provenance attestation provenance

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

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.1.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.

v0.1.37

1 finding
LOW No provenance attestation provenance

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

v0.1.36

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: siddhesh.shirdhankar.

LOW No provenance attestation provenance

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

v0.1.35

2 findings
HIGH Publisher changed: siddhesh.shirdhankar → godwin.pinto (on 2025-11-27) provenance

This version was published by a different npm account than previous versions on 2025-11-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.34

1 finding
LOW No provenance attestation provenance

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

v0.1.33

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.

v0.1.32

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.