@aurora-is-near/intents-swap-widget
Provides components and hooks to build your own Intents swap widget
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:@near-wallet-selector/my-near-wallet | AI (phantom-deps): Likely imported in bundled source files. | ai | |
| phantom-deps | phantom-dep:@aurora-is-near/eslint-config | AI (phantom-deps): Same-org eslint config; declared dep, likely used in build tooling. | ai | |
| phantom-deps | phantom-dep:qs | AI (phantom-deps): Likely imported transitively or in bundled source files. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Likely imported in bundled source files. | ai | |
| phantom-deps | phantom-dep:debounce | AI (phantom-deps): Likely imported in bundled source files. | ai | |
| phantom-deps | phantom-dep:proxy-memoize | AI (phantom-deps): Likely imported in bundled source files. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-icons | AI (phantom-deps): Likely imported in bundled source files. | ai | |
| phantom-deps | phantom-dep:@near-wallet-selector/modal-ui | AI (phantom-deps): Likely imported in bundled source files. | ai | |
| phantom-deps | phantom-dep:@near-wallet-selector/react-hook | AI (phantom-deps): Likely imported in bundled source files. | ai | |
| phantom-deps | phantom-dep:@near-wallet-selector/meteor-wallet | AI (phantom-deps): Likely imported in bundled source files. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding used for cryptographic signature handling in useCompatibilityCheck.ts — legitimate pattern for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 7.9.0 | 33 / 0 | |
| 7.8.0 | 33 / 0 | |
| 7.7.1 | 33 / 0 | |
| 7.7.0 | 33 / 0 | |
| 7.6.0 | 33 / 0 | |
| 7.5.0 | 33 / 0 | |
| 7.4.2 | 33 / 0 | |
| 7.4.1 | 33 / 0 | |
| 7.4.0 | 33 / 0 | |
| 7.3.3 | 33 / 0 | |
| 7.3.2 | 33 / 0 | |
| 7.3.1 | 33 / 0 | |
| 7.3.0 | 33 / 0 | |
| 7.2.2 | 33 / 0 | |
| 7.2.1 | 33 / 0 | |
| 7.2.0 | 33 / 0 | |
| 7.1.1 | 33 / 0 | |
| 7.1.0 | 33 / 0 | |
| 7.0.0 | 33 / 0 | |
| 6.24.2 | 37 / 0 | |
| 6.24.1 | 37 / 0 | |
| 6.24.0 | 37 / 0 | |
| 3.2.0 | 38 / 0 | |
| 2.38.0 | 38 / 0 | |
| 2.19.2 | 39 / 0 | |
| 2.19.1 | 39 / 0 | |
| 2.19.0 | 39 / 0 |
v7.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.