@midwayjs/validate
Midway Component for mongoose
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:validator | AI (typosquat): Scoped @midwayjs package in a long-established framework; not a typosquat of 'validator'. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package with sparse metadata; 189 versions and 2.8k downloads confirm legitimacy. | ai |
Versions (showing 40 of 140)
| Version | Deps | Published |
|---|---|---|
| 3.4.12 | 2 / 5 | |
| 3.4.11 | 2 / 5 | |
| 3.4.10 | 2 / 5 | |
| 3.4.9 | 2 / 5 | |
| 3.4.7 | 2 / 5 | |
| 3.4.6 | 2 / 5 | |
| 3.4.5 | 2 / 5 | |
| 3.4.4 | 2 / 5 | |
| 3.4.3 | 2 / 5 | |
| 3.4.1 | 2 / 5 | |
| 3.4.0 | 2 / 5 | |
| 3.3.11 | 2 / 5 | |
| 3.3.9 | 2 / 5 | |
| 3.3.6 | 2 / 5 | |
| 3.3.5 | 2 / 5 | |
| 3.3.4 | 2 / 5 | |
| 3.3.2 | 2 / 5 | |
| 3.3.1 | 2 / 5 | |
| 3.3.0 | 2 / 5 | |
| 3.2.2 | 2 / 5 | |
| 3.2.1 | 2 / 5 | |
| 3.2.0 | 2 / 5 | |
| 3.1.6 | 2 / 5 | |
| 3.1.5 | 2 / 5 | |
| 3.1.2 | 2 / 5 | |
| 3.1.1 | 2 / 5 | |
| 3.1.0 | 2 / 5 | |
| 3.0.13 | 2 / 5 | |
| 3.0.11 | 2 / 5 | |
| 3.0.10 | 2 / 5 | |
| 3.0.9 | 2 / 5 | |
| 3.0.8 | 2 / 5 | |
| 3.0.7 | 2 / 5 | |
| 3.0.6 | 2 / 5 | |
| 3.0.5 | 2 / 5 | |
| 3.0.4 | 2 / 5 | |
| 3.0.3 | 2 / 5 | |
| 3.0.2 | 2 / 5 | |
| 3.0.1 | 2 / 5 | |
| 3.0.0 | 2 / 5 |
v3.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.