Issues

Release process is manual and undocumented — versioning and publishing are error-prone

Sorokit/core#802 · opened

on Oct 15, 2026

3

Code coverage is not tracked or reported — unknown coverage percentage

Sorokit/core#801 · opened

on Oct 15, 2026

4

CI workflow does not include security scanning or SAST tools — vulnerabilities slip through

Sorokit/core#800 · opened

on Oct 15, 2026

4

CONTRIBUTING.md is missing or outdated — developers cannot contribute effectively

Sorokit/core#799 · opened

on Oct 15, 2026

2

README does not include minimal working examples for common tasks — new users are lost

Sorokit/core#798 · opened

on Oct 15, 2026

TypeScript configuration does not enforce strict mode — type safety gaps are not caught

Sorokit/core#797 · opened

on Oct 15, 2026

Dependency on the Stellar SDK is not pinned — major version bumps may break sorokit-core

Sorokit/core#796 · opened

on Oct 15, 2026

`package.json` exports field does not match actual source structure — tree-shaking is broken

Sorokit/core#795 · opened

on Oct 15, 2026

Error handling across the SDK is inconsistent — some functions throw, others return `SorokitResult`

Sorokit/core#794 · opened

on Oct 15, 2026

`core.ts` does not document which features require opt-in configuration — callers miss required setup steps

Sorokit/core#793 · opened

on Oct 15, 2026

`index.ts` in shared module exports internal utilities without a stability guarantee — consumer code may break on patch updates

Sorokit/core#792 · opened

on Oct 15, 2026

`core.ts` re-exports do not match the actual module structure — `import` paths may be wrong

Sorokit/core#791 · opened

on Oct 15, 2026

`types-validation.ts` exports types without runtime validators — no way to validate data at runtime

Sorokit/core#790 · opened

on Oct 15, 2026

`getNetworkConfig` does not validate RPC and Horizon URLs before returning them — bad URLs are silently accepted

Sorokit/core#789 · opened

on Oct 15, 2026

`index.ts` in governance module is empty — no exported functions

Sorokit/core#788 · opened

on Oct 15, 2026

`mockAbstraction.ts` does not support partial mocking — all methods must be overridden or tests become brittle

Sorokit/core#787 · opened

on Oct 15, 2026

`createSorokitClient` exported type does not match runtime implementation — TypeScript errors on proper usage

Sorokit/core#786 · opened

on Oct 15, 2026

`governance.ts` integration does not track proposal voting state — callers cannot query their own votes

Sorokit/core#785 · opened

on Oct 15, 2026

`didSupport.ts` does not validate DID document structure — accepts malformed DIDs

Sorokit/core#784 · opened

on Oct 15, 2026

`sep6Flow.ts` does not validate anchor withdrawal amounts — allows zero or negative amounts

Sorokit/core#783 · opened

on Oct 15, 2026

`sep7Handler.ts` does not validate SEP-7 link parameters — allows injection of arbitrary transaction modifications

Sorokit/core#782 · opened

on Oct 15, 2026

`sep31DirectPayment.ts` does not enforce transaction ID uniqueness — allows duplicate submissions

Sorokit/core#781 · opened

on Oct 15, 2026

5

`LazyProxy` in `lazy/index.ts` does not handle initialization errors — swallows exceptions and returns undefined

Sorokit/core#780 · opened

on Oct 15, 2026

5

`zeroKnowledge.ts` in privacy module does not validate proof complexity — allows unbounded-size proofs

Sorokit/core#779 · opened

on Oct 15, 2026

3

`sep24Flow.ts` does not handle interactive flow interactive redirects with state validation — potential CSRF vulnerability

Sorokit/core#778 · opened

on Oct 15, 2026

4

Navigation Menu

Repository navigation

Issues

Release process is manual and undocumented — versioning and publishing are error-prone

Code coverage is not tracked or reported — unknown coverage percentage

CI workflow does not include security scanning or SAST tools — vulnerabilities slip through

CONTRIBUTING.md is missing or outdated — developers cannot contribute effectively

README does not include minimal working examples for common tasks — new users are lost

TypeScript configuration does not enforce strict mode — type safety gaps are not caught

Dependency on the Stellar SDK is not pinned — major version bumps may break sorokit-core

`package.json` exports field does not match actual source structure — tree-shaking is broken

Error handling across the SDK is inconsistent — some functions throw, others return `SorokitResult`

`core.ts` does not document which features require opt-in configuration — callers miss required setup steps

`index.ts` in shared module exports internal utilities without a stability guarantee — consumer code may break on patch updates

`core.ts` re-exports do not match the actual module structure — `import` paths may be wrong

`types-validation.ts` exports types without runtime validators — no way to validate data at runtime

`getNetworkConfig` does not validate RPC and Horizon URLs before returning them — bad URLs are silently accepted

`index.ts` in governance module is empty — no exported functions

`mockAbstraction.ts` does not support partial mocking — all methods must be overridden or tests become brittle

`createSorokitClient` exported type does not match runtime implementation — TypeScript errors on proper usage

`governance.ts` integration does not track proposal voting state — callers cannot query their own votes

`didSupport.ts` does not validate DID document structure — accepts malformed DIDs

`sep6Flow.ts` does not validate anchor withdrawal amounts — allows zero or negative amounts

`sep7Handler.ts` does not validate SEP-7 link parameters — allows injection of arbitrary transaction modifications

`sep31DirectPayment.ts` does not enforce transaction ID uniqueness — allows duplicate submissions

`LazyProxy` in `lazy/index.ts` does not handle initialization errors — swallows exceptions and returns undefined

`zeroKnowledge.ts` in privacy module does not validate proof complexity — allows unbounded-size proofs

`sep24Flow.ts` does not handle interactive flow interactive redirects with state validation — potential CSRF vulnerability