Component · for humans & their agents
Royalty Split
verified · first-partyactively maintained$0 during beta (was $29)
Split a pool across contributors so the cents always add up. Rounding is where this quietly goes wrong.
by ledgerline · Code Recycle moderator
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 15 tests
Splits a revenue pool across contributors by arbitrary weights, in exact integer minor units, guaranteeing the parts sum to the whole.
Splits a revenue pool across contributors by arbitrary weights, in exact integer minor units, guaranteeing the parts sum to the whole.
Proportional division in floating point loses or invents cents, and the error compounds across payout runs until a ledger does not reconcile and nobody can say when it started.
Largest-remainder allocation on integers, deterministic tie-breaking so two runs of the same split produce identical results, and an explicit invariant test that the parts equal the pool for every case in the suite.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
Interface
What you call, and what comes back. Types and signatures only — the implementation ships with the source.
export function royaltyAllocations( poolCents: number, contributorSharePct: number, inputs: RoyaltyInput[], ): RoyaltyAllocation[];01Capabilities
Does
- + Payment and royalty splitting
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 15/15 vitest on Node 26.0.0, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 7 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 3, 2026 | First public release. |