Bug: npm ci fails on main — package-lock.json has a renamed git dep and npmmirror.com URLs, so all CI is red

[Jaydbrown]

What

npm ci fails in CI on every recent main commit (and locally), so the
Lint & typecheck and Unit tests jobs never get to run — every open PR
inherits a red "CI" check regardless of its contents.

Two independent problems in package-lock.json:

1. SDK git dependency points at a repo that no longer exists

"@conduit-protocol/sdk": "github:conduit-protocol/conduit-sdk",
...
"node_modules/@conduit-protocol/sdk": {
  "resolved": "git+ssh://git@github.com/conduit-protocol/conduit-sdk.git#f364474..."
}

conduit-protocol/conduit-sdk was renamed to conduit-protocol/streamFi-sdk.
The git+ssh:// form also can't authenticate on the CI runner even for a repo
that does exist.

2. ~30 packages resolved against a regional mirror

"resolved": "https://registry.npmmirror.com/geist/-/geist-1.7.2.tgz"
"resolved": "https://registry.npmmirror.com/next-themes/-/next-themes-0.4.6.tgz"
...

registry.npmmirror.com (an npm mirror) is baked into the lockfile from a
contributor's local environment. CI (and anyone outside that network) gets
ENOTFOUND registry.npmmirror.com.

Fix

Regenerate package-lock.json on main against registry.npmjs.org, with
the SDK dependency spec updated to the current repo — e.g.
github:conduit-protocol/streamFi-sdk (HTTPS, not git+ssh), or publish
@conduit-protocol/sdk to npm and depend on the version.

Add a CI guard (grep -q npmmirror package-lock.json && exit 1) so a
mirror-polluted lockfile can't merge again.

Impact

No app PR can pass CI until this is fixed. Blocks #403 and every other open PR.

[temieehade-coder]

@temieehade-coder has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, i can fix this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @temieehade-coder to this issue.

[SamixYasuke]

@SamixYasuke has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'd fix Fix package-lock.json by updating the SDK dependency to github:conduit-protocol/streamFi-sdk over HTTPS and regenerating the lockfile against registry.npmjs.org, removing all registry.npmmirror.com entries. Add a CI guard that fails when npmmirror.com appears in the lockfile, then verify npm ci, lint/typecheck, and unit tests pass.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @SamixYasuke to this issue.

[DonaldXoftDev]

@DonaldXoftDev has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I will like to work on this issue please assign it to me 🙏🙏

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DonaldXoftDev to this issue.

[0takuc0mrade]

@0takuc0mrade has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @0takuc0mrade to this issue.

[Muyideen-js]

@Muyideen-js has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I can fix this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Muyideen-js to this issue.

[frank0277]

@frank0277 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer please I would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @frank0277 to this issue.

[drips-wave]

Congratulations, @0takuc0mrade! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @0takuc0mrade: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @0takuc0mrade as part of the Stellar Wave Program's 8th Wave 🥳

😎 @0takuc0mrade: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.