@abp/jquery-validation-unobtrusive
ABP Framework is a complete open-source infrastructure to create modern web applications by following the best practices and conventions of software development. This package is a part of the [ABP Framework](https://abp.io) and contains client-side files.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:jquery-validation-unobtrusive | AI (dependencies): jquery-validation-unobtrusive is a well-known Microsoft ASP.NET library; stable dependency for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): ABP npm wrapper packages are intentionally tiny shims with link-heavy READMEs; not spam. | ai | |
| phantom-deps | phantom-dep:@abp/jquery-validation | AI (phantom-deps): Thin wrapper package; declared dep not directly imported by design in ABP shim packages. | ai | |
| phantom-deps | phantom-dep:jquery-validation-unobtrusive | AI (phantom-deps): Thin wrapper package; declared dep referenced in config but not directly imported by design. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 10.4.1 | 2 / 0 | |
| 10.4.0 | 2 / 0 | |
| 10.3.0 | 2 / 0 | |
| 10.2.1 | 2 / 0 | |
| 10.2.0 | 2 / 0 | |
| 10.0.0 | 2 / 0 |
v10.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.