Methodology · v3.2

DEHÉcosystème développeurs

Developer ecosystem strength for {legal_name} — organic adoption signals across open code platforms. EXTRACTION RULES: ZERO-IS-ABSENT (mandatory, per sub-signal): the bottom bucket is reserved for a vendor whose handle was CONFIDENTLY identified and name-matched to {legal_name} and genuinely has a small footprint. If you CANNOT confidently identify and name-match the vendor's GitHub org / npm-or-PyPI scope / StackOverflow tag (the org name on GitHub rarely matches legal_name; npm scope often differs from brand), OMIT that sub-signal entirely — DO NOT emit the bottom bucket from a not-found / name-match failure (CLAUDE.md #5: never invent a number from weak evidence). A cited, name-matched source_url is REQUIRED before any value (including a bottom bucket) is emitted. Return type="composite_signal" with up to 4 sub-signals: (a) github_stars_aggregate — sum of stars across the vendor's top 5 public repos (cite github.com/<org>); bucket <1k→25, 1-10k→55, 10-50k→75, 50k-500k→88, 500k+→95; (b) npm_pypi_weekly_downloads — for SaaS/cloud/AI vendors with public SDKs, sum weekly npm or PyPI downloads of their official packages (cite npmjs.com/~<org> or pypi.org/user/<org>); <10k→25, 10-100k→55, 100k-1M→75, 1M-10M→88, 10M+→95; (c) external_contributors_12mo — distinct external contributor count across the vendor's top repos (cite github-stats.com or repo Insights pages); <20→30, 20-100→60, 100-500→80, 500+→92; (d) stackoverflow_tag_questions_12mo — questions tagged with vendor product name in last 12mo (cite stackoverflow.com/questions/tagged/<vendor>); <50→30, 50-500→60, 500-5000→80, 5000+→92. Server applies composite_signal_score. If the vendor's handles cannot be identified at all, or it has no public OSS presence (pure closed-source enterprise), return type="absent" reason="no_oss_presence" — DO NOT fabricate sub-signal values.