@anonvote/crypto is not published — npm badge is broken and core cannot install it

[grantfox-oss]

The README shows an npm version badge linking to
https://www.npmjs.com/package/@anonvote/crypto but the
package does not exist on npm. The badge renders as broken.
core lists @anonvote/crypto as a dependency in its
README but cannot actually install it via npm install
because the package has never been published. Any
contributor following the getting started guide in
core hits a missing package error immediately.

The package.json has prepublishOnly set to run build
and test before publish, and the version is at 1.4.0
suggesting publish was intended but never completed.
There is also an open PR aligning crypto primitives
with the type spec — publish should not happen until
that PR is reviewed and merged.

Scope:

• Review and merge or close PR feat: align crypto primitives with @anonvote/crypto type spec #11 before publishing
• Confirm npm run build produces a clean dist/ with
  correct .js and .d.ts files for all exports
• Confirm npm test passes with no failures
• Publish to npm under the @AnonVote scope — requires
  an npm org at @AnonVote to exist or be created
• Verify the npm badge in the README resolves after
  publish
• Add a note in core's getting started guide clarifying
  that @anonvote/crypto must be available on npm for
  npm install to work

Acceptance Criteria:

• PR feat: align crypto primitives with @anonvote/crypto type spec #11 reviewed and merged before publish
• npm run build produces dist/ with no TypeScript errors
• npm test passes cleanly
• @anonvote/crypto visible at npmjs.com/package/@anonvote/crypto
• npm install @anonvote/crypto works from a fresh directory
• README badge resolves with the correct version number

[jaynomyaro]

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[Damidesign]

I would love to tackle this bug and restore the publishing pipeline for @anonvote/crypto.

When a core package fails to publish, it creates a severe bottleneck for the entire workspace and halts downstream development. Resolving these registry and workflow blocks is an area I am highly familiar with. I regularly handle complex repository management and set up robust CI/CD pipelines, giving me the technical insight to quickly diagnose why the package is stalling.

Whether the root cause is a misconfigured package.json, a broken GitHub Actions publishing step, or an authentication token failure, I can pinpoint the issue and implement a permanent fix. I am ready to audit the workflow, fix the broken npm badge, and ensure that core can seamlessly install the dependency once again.

I would appreciate being assigned to this issue