Methodology

How Produtype reads readiness

Produtype does not ask whether a repository has good code alone. It asks whether the repository has the capabilities expected for the product it is becoming.

Observed code readiness

Measures deterministic code signals: structure, obvious risks, implementation completeness, and operational cues.

Expected capability score

Compares the repository against the selected product profile and the capabilities that profile normally requires.

Final product-readiness score

Combines observed readiness with expected product capability coverage to produce the headline score.

Product profiles

Produtype can evaluate a repository as a static site, internal tool, B2C app, B2B SaaS, AI SaaS, marketplace, or observed-only. The chosen profile changes the capability expectations.

Why wanderstack scores 89 observed-only and 53 as B2B SaaS

Observed-only mode sees a clean repository with strong code hygiene. B2B SaaS mode asks different questions: auth, tenancy, GDPR, billing, observability, and deployment readiness.

The code may look healthy, but the product is not yet ready for a business customer experience.

Not a vulnerability scanner

Produtype is not a security certification tool and does not claim compliance certification. It helps teams understand product readiness, capability gaps, and remediation priorities.

Security-related concerns can appear in the findings, but the core question is broader than vulnerabilities: does the repository have the product capabilities expected for launch?