yup
Dead simple Object schema validation
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): yup ships dual CJS/ESM builds; lodash-es is used in the ESM output. This is a stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): @types/lodash as a runtime dep is unusual but benign — used for TypeScript consumers. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is injected by Babel transforms at build time; not directly imported in source. Standard pattern for Babel-compiled packages. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is in gulpfile.js (dev build tooling only), not in runtime code shipped to consumers. Standard Gulp visitor-loading pattern; no risk to package users. | ai | |
| phantom-deps | phantom-dep:fn-name | AI (phantom-deps): fn-name is explicitly declared as a runtime dependency in package.json; this is a false positive from the phantom-deps analyzer. | ai |
Versions (showing 19 of 119)
| Version | Deps | Published |
|---|---|---|
| 0.7.4 | 5 / 12 | |
| 0.7.3 | 5 / 12 | |
| 0.7.2 | 5 / 12 | |
| 0.7.1 | 4 / 12 | |
| 0.7.0 | 4 / 12 | |
| 0.6.3 | 4 / 11 | |
| 0.6.2 | 4 / 11 | |
| 0.6.1 | 4 / 11 | |
| 0.6.0 | 4 / 11 | |
| 0.5.1 | 5 / 10 | |
| 0.5.0 | 5 / 10 | |
| 0.4.2 | 4 / 7 | |
| 0.4.1 | 4 / 7 | |
| 0.3.1 | 4 / 7 | |
| 0.3.0 | 4 / 7 | |
| 0.2.0 | 4 / 7 | |
| 0.1.2 | 4 / 7 | |
| 0.1.1 | 4 / 7 | |
| 0.1.0 | 4 / 7 |
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.