Arkade published version 0.1.7 of its swap package on November 17 with release notes linking dependency maintenance, a private security-reporting policy and a transaction-history handling fix in its TypeScript SDK repository. The useful detail is the scope: the dependency alerts described by the maintainers were not in the SDK’s runtime dependencies.
A software development kit supplies components that application developers build on. A new repository release can therefore matter to wallet builders without proving that every wallet using the project has already deployed the changes. The release tag and an application’s installed version answer different questions.
What the dependency findings covered
The underlying dependency pull request says an audit reported three critical and 36 high-severity advisories in development tooling or Expo and async-storage peer installations. The maintainer explicitly excludes the SDK’s runtime dependencies from that set.
The change raises dependency overrides, moves the Vitest test tools to a newer version and adds a high-severity audit check to continuous integration. The maintainer reports passing lint, build, documentation-build and unit checks, while noting that regtest integration suites were not run. Those are reported checks, not tests performed by Coins Rate.
Severity labels describe the dependency advisories. They do not, on their own, establish an exploitable path in a deployed wallet or a theft of user funds. Conversely, removing high-severity findings from one audit does not certify every part of a system as safe. Reading which components were involved is more useful than treating the largest severity label as a complete risk assessment.
A separate repair to address watching
Another linked pull request addresses the initialization of address monitoring. Its author says a transaction-history entry without a status field could cause an unhandled error while the initial history was being processed. The change places that processing inside the existing failure-handling path, allowing a fallback to the first polling pass.
This is a concrete reliability issue at the boundary between returned history data and the code consuming it. It is not a claim that a blockchain transaction was reversed or that an address balance disappeared. For an application maintainer, the relevant follow-up is how the application behaves when history data is incomplete or malformed.
Private reports get an explicit route
The release also links a repository security policy adopted through a separate pull request. That policy uses GitHub private security advisories as the primary vulnerability-reporting channel. The maintainer’s description says it covers source code, release artifacts, published packages and supported deployments, with a coordinated disclosure process.
A reporting procedure gives researchers a defined way to raise a sensitive finding. It does not mean a new vulnerability has been discovered. Similarly, the existence of a public fix should not be recast as evidence of a prior attack without an incident report or other supporting record.
The next check is the application version
Developers assessing the release should identify their actual package versions, read the linked changes and test the paths their own application uses. End users should look to their wallet provider’s release information rather than assume that a library tag is an instruction to move funds.
Our wallet and custody guide explains the different responsibilities around key control. The crypto scam guide covers why an unsolicited “upgrade” message deserves scrutiny. The documented news here is maintenance and clearer reporting, with specific technical limits, not a blanket security guarantee.