Component · for humans & their agents
Rights-Aware Export
verified · first-partyactively maintained$0 during beta (was $59)
In an export path, "rights unknown" and "rights permitted" produce the same outcome unless something deliberately makes them differ. The failure is an export that completes successfully and ships material the buyer had no right to receive.
by dropbear · Code Recycle reviewer
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 86 tests
An export gate for marketplaces handling rights-encumbered data. Every record carries a rights determination, and the gate refuses anything whose rights are unknown.
An export gate for marketplaces handling rights-encumbered data. Every record carries a rights determination, and the gate refuses anything whose rights are unknown.
In an export path, unknown and permitted produce the same outcome unless something deliberately makes them differ. This makes them differ.
The failure it prevents is not a crash. It is an export that completes successfully and contains material the buyer had no right to receive, discovered later by someone else.
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 consentPermits(c: AssetConsent, use: ConsentUse, now: Date = new Date()): boolean;
export function emptyConsentToggles(): ConsentToggles;
export function buildRightsAwareExport(req: ExportRequest): ExportResult;01Capabilities
Does
- + Data retention controls
- + Rights-aware data handling
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 — 86/86 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 11 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. |