Receipts
Trust the trail more than the logo.
Nostr products are often small, fast-moving and maintained by tiny teams. That energy is part of the charm. It is also a risk. A client can ask for signing authority. A relay can shape visibility. A wallet connection can move money. A moderation tool can hide people. Software reputation therefore belongs in governance, not only in Apps.
The useful question is simple: what can this software touch, and what proof can you inspect before trusting it?
Maintenance is a trust signal
A repository with active commits, issues, releases and public maintainers gives you a different risk picture than an abandoned binary. Open source is not automatic safety, but it creates a trail. You can see whether bugs are fixed, whether security issues are handled, whether dependencies move and whether other builders rely on the code.
Screenshots are weak receipts
Screenshots can be useful for explaining a UI, but they are poor proof when conflict starts. Signed events, commit links, release notes, issue threads, NIP references and reproducible behavior are stronger. A good governance archive should prefer direct links over dramatic screenshots.
Permissions matter more than polish
A beautiful client that asks for raw private-key entry deserves more caution than a rough interface using a safer signer. A wallet connection with broad permissions deserves more scrutiny than a limited budget. A moderation tool that hides sources deserves more skepticism than one that shows the rule.
Permissions are a reputation surface
Software reputation is not only whether a maintainer is famous. It is whether the product asks for appropriate power. A client that requests a signer permission for a narrow action is different from a website asking you to paste an nsec. A wallet tool with spending limits is different from one with broad authority. A relay management tool with clear authentication is different from a hidden admin panel.
That is why permissions belong in the governance route. They decide who can act as you, spend for you, hide things from you or publish under your key. The more power a product requests, the more public receipts it should provide.
Community memory can protect newcomers
Nostr has many small tools with uneven documentation. Public notes, GitHub issues, app profiles, maintainer identities and repeated user reports become part of the safety layer. A good archive does not turn that memory into gossip. It turns it into links you can inspect before trusting a product.
The exit test is simple
Before trusting software, ask what happens if it disappears. Can you export keys? Can you switch clients? Can you revoke a wallet connection? Can you find your media? Can another relay serve your events? If the answer is no, the product may still be useful, but it is asking for platform-style trust.