saascode

Tooltrust

A managed extension mirror and trust registry that preserves upstream artifacts, verifies signatures and software bills of materials, records review evidence, enforces team install policy, and observes declared external-service behavior without promising that a vetted extension is safe.

Genesis score5.62/10
Make Tooltrust real.0/500
500 more votes and Tooltrust is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
300M+Monthly registry downloads
0Enterprise governance product found
Never assumedTrusted means safe
The case

The supplied research confirms a machine-scale open extension registry, a new managed registry service, active security work, free signing and software-bill-of-materials standards, and no identified enterprise product focused on extension governance. It does not verify the two proposed APIs or prove that the registry operator has committed never to build governance. Tooltrust's opportunity is a customer-controlled mirror, evidence history and enforceable install policy. Signature, scan and review results must remain bounded evidence rather than a safety certification.

Who pays — and why

The developer platform, application security, endpoint engineering, compliance, or software-supply-chain team governing extensions across a large organization.

What it unlocks
An immutable mirror linking each extension version to upstream source, checksum, publisher identity, signature, package inventory, license evidence and scan results
A review registry that separates automated findings, analyst disposition, approved scope, exceptions, expiry, revocation and unresolved evidence
Team and environment install policy with client acknowledgment, inventory readback, external-service declarations and incident response
How Genesis scored it
5.62across seven criteria
tension 6temporal 5blindspot 5buyer 6leverage 7convergence 5why-not 5
7
Asymmetric leverage

Mirroring, evidence, policy and fleet inventory scale through software after difficult integrations.

6
Productive tension

Central control must reduce extension risk without freezing developer workflows or creating false trust.

5
Why nobody did it

New registry infrastructure helps but does not prove the barrier that prevented governance.

Why it scored well

The registry scale, security primitives, enterprise buyer and extension-specific governance gap create a concrete product surface.

What's holding it back

No connected-idea convergence exists, proposed APIs are unverified, the incumbent blind spot is asserted rather than proven, and deep endpoint integration is required.

Signals detected5 sources crossed
Signalregistry research carried in Genesis

Signalecosystem research carried in Genesis

Signalsupply-chain standards research carried in Genesis

Signalcompetitive scan carried in Genesis

SignalGenesis integration limitation

Direction brieftooltrust.md
tooltrust.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.