Surveyor is getting close to v1.0.0 and I would like blunt opinions before I freeze the first stable release. The project has reached the point where the core shape is there but this is still the right time to catch weak spots in the UX, docs, naming, output, scope or overall direction before I lock in the 1.0 contract. If you have a few minutes, I would really value feedback on things like: whether the project positioning is clear whether the README and docs make sense on first read whether the command model feels coherent whether the reports and outputs are useful and understandable whether anything feels awkward, overcomplicated, misleading, or under-explained what looks strong, and what still looks weak Blunt feedback is welcome. I would rather hear that something is unclear or poorly designed now than pretend it is fine and carry that into v1.0.x For genuine bugs, please use Issues. For broader opinions, questions, design thoughts or “this feels off” feedback use the Discussions. If you have found Surveyor genuinely useful, please feel free to share in Use Cases as well. Thank you to everyone who has taken a look at Surveyor. The goal is to make v1.0.x clean, credible and genuinely useful to a wider audience.

Surveyor

TLS-first cryptographic inventory and migration readiness

TLS-first cryptographic inventory and migration readiness