Repository navigation
Fix/phase 2 remediation - #30
Conversation
Fixes 205. deriveFundingExternalId hashed only vault:network:bond:bondIndex: It now includes the persisted funding generation to ensure uniqueness across retries.
[FIREHOG-BYPASS] false positive
[FIREHOG-BYPASS] false positive
…ansfer before adopting it
…nd BTC recovery calls
…e an unreadable transfer, restore a doc block
Regenerated because no lockfile is committed. Installed with npm ci and tested before this commit.
|
Semgrep found 798
🟠 High severity issue identified in your code: package-lock.json contains a reference to a public package registry or CDN (https://registry.npmjs.org/commander/-/commander-9.5.0.tgz). Dependencies must be resolved through the approved internal JFrog/Artifactory registry. Update your .npmrc to point at the approved registry, delete node_modules and package-lock.json, then re-run |
Regenerated because no lockfile is committed. Installed with npm ci and tested before this commit.
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
|
Semgrep found 66
🟠 High severity issue identified in your code: package-lock.json contains a reference to a public package registry or CDN (https://registry.npmjs.org/update-browserslist-db/-/update-browserslist-db-1.3.3.tgz). Dependencies must be resolved through the approved internal JFrog/Artifactory registry. Update your .npmrc to point at the approved registry, delete node_modules and package-lock.json, then re-run |
…uire atomic lock-record stores
…ord before broadcasting a re-lock
…rds and reward claims
…e workflow changes
|
Semgrep found 7
🟠 High severity issue identified in your code: Risk: Affected versions of body-parser are vulnerable to Uncaught Exception. When a request carries a Content-Encoding header (gzip, deflate, br), body-parser pipes the body into a zlib decompression stream that remains piped without an error listener after the body is read. An unauthenticated attacker can send a valid compressed frame followed by trailing bytes, causing the decoder to emit an uncaught error that crashes the Node.js process (denial of service). All parsers (json, raw, text, urlencoded, and the Express re-exports) are affected unless the Fix: Upgrade this library to at least version 2.4.0 at stacks-fireblocks-sdk/package-lock.json:3907. Reference(s): https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-108189, GHSA-27r3-jxmh-p828, CVE-2026-111181 |
…ding must not start again
No description provided.