@abp/uppy
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): ABP framework publishes many scoped packages; gap likely reflects org release cadence, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): ABP framework integration shim; tiny payload and link-dump README are expected for this package family. | ai | |
| phantom-deps | phantom-dep:uppy | AI (phantom-deps): Uppy is a peer/re-exported dep in an integration shim; not directly imported in source is expected. | ai | |
| phantom-deps | phantom-dep:@abp/core | AI (phantom-deps): Same-org dependency; phantom-dep false positive for ABP framework packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 10.4.0 | 2 / 0 | |
| 10.3.0 | 2 / 0 | |
| 10.2.1 | 2 / 0 | |
| 10.2.0 | 2 / 0 | |
| 10.0.1 | 2 / 0 | |
| 10.0.0 | 2 / 0 | |
| 9.3.7 | 2 / 0 |
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.1
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.
v9.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.