@swapkit/plugins
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file-transition:dist/src/evm/index.cjs | AI (source-diff): esbuild-bundled CJS interop preamble, not obfuscation; readable plugin logic, no exfil/exec. | ai | |
| source-diff | obfuscated-file-transition:dist/src/radix/index.cjs | AI (source-diff): esbuild-bundled CJS interop preamble, not obfuscation; readable plugin logic, no exfil/exec. | ai | |
| source-diff | obfuscated-file-transition:dist/src/solana/index.cjs | AI (source-diff): esbuild-bundled CJS interop preamble, not obfuscation; readable plugin logic, no exfil/exec. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding base64 Solana VersionedTransaction is standard web3 pattern; not obfuscation. | ai | |
| phantom-deps | phantom-dep:@mysten/sui | AI (phantom-deps): @mysten/sui is declared as a runtime dep in package.json; phantom-dep heuristic misfires for this package. | ai |
Versions (showing 51 of 108)
| Version | Deps | Published |
|---|---|---|
| 4.7.4 | 3 / 5 | |
| 4.7.3 | 3 / 5 | |
| 4.7.2 | 3 / 5 | |
| 4.7.1 | 3 / 5 | |
| 4.7.0 | 3 / 5 | |
| 4.6.64 | 3 / 5 | |
| 4.6.63 | 3 / 5 | |
| 4.6.61 | 3 / 5 | |
| 4.6.60 | 3 / 5 | |
| 4.6.59 | 3 / 5 | |
| 4.6.58 | 3 / 5 | |
| 4.6.57 | 3 / 4 | |
| 4.6.56 | 3 / 4 | |
| 4.6.55 | 3 / 4 | |
| 4.6.54 | 3 / 4 | |
| 4.6.53 | 3 / 4 | |
| 4.6.52 | 3 / 4 | |
| 4.6.51 | 3 / 4 | |
| 4.6.50 | 3 / 4 | |
| 4.6.49 | 3 / 4 | |
| 4.6.48 | 3 / 4 | |
| 4.6.47 | 3 / 4 | |
| 4.6.46 | 3 / 4 | |
| 4.6.45 | 3 / 4 | |
| 4.6.44 | 3 / 4 | |
| 4.6.43 | 3 / 4 | |
| 4.6.42 | 3 / 4 | |
| 4.6.41 | 3 / 4 | |
| 4.6.40 | 3 / 4 | |
| 4.6.39 | 3 / 4 | |
| 4.6.38 | 3 / 4 | |
| 4.6.37 | 11 / 4 | |
| 4.6.36 | 11 / 4 | |
| 4.6.35 | 11 / 4 | |
| 4.6.34 | 11 / 4 | |
| 4.6.33 | 11 / 4 | |
| 4.6.32 | 11 / 4 | |
| 4.6.31 | 11 / 4 | |
| 4.6.30 | 11 / 4 | |
| 4.6.29 | 11 / 4 | |
| 4.6.28 | 11 / 4 | |
| 4.6.27 | 11 / 4 | |
| 4.6.26 | 11 / 4 | |
| 4.6.25 | 11 / 4 | |
| 4.6.24 | 11 / 4 | |
| 4.6.23 | 11 / 4 | |
| 4.6.22 | 11 / 4 | |
| 4.6.21 | 11 / 4 | |
| 4.6.20 | 11 / 4 | |
| 4.6.19 | 11 / 4 | |
| 4.6.18 | 11 / 4 |
v4.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.3
4 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
4 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
4 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
4 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.