@abp/anchor-js
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:anchor-js | AI (dependencies): anchor-js is a legitimate, well-known library; its use here is intentional and documented. | ai | |
| bogus-package | bogus-package | AI (bogus-package): ABP framework routinely publishes thin wrapper packages with minimal code; link-dump README is typical of their ecosystem docs style. | ai | |
| phantom-deps | phantom-dep:@abp/core | AI (phantom-deps): Same-org peer dependency pattern; not directly imported but used as a framework peer across ABP packages. | ai | |
| phantom-deps | phantom-dep:anchor-js | AI (phantom-deps): Referenced in config files per finding; consistent with a wrapper package that re-exports anchor-js. | ai |
Versions (showing 12 of 12)
| 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.1.1 | 2 / 0 | |
| 10.1.0 | 2 / 0 | |
| 10.0.3 | 2 / 0 | |
| 10.0.2 | 2 / 0 | |
| 10.0.1 | 2 / 0 | |
| 10.0.0 | 2 / 0 | |
| 9.3.7 | 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.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.