reference-design-contract vs lineage-skill
Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.
- Type
- reference-design-contractSkill
- lineage-skillSkill
- Category
- reference-design-contractProductivity
- lineage-skillProductivity
- GitHub stars
- reference-design-contract0
- lineage-skill378
- Trust score
- reference-design-contractNot yet assessed
- lineage-skill81/100 · Excellent
- Community rating
- reference-design-contractNo reviews yet
- lineage-skillNo reviews yet
- Last commit
- reference-design-contractUnknown
- lineage-skill7 days ago
- Licence
- reference-design-contractNone declared
- lineage-skillApache-2.0
- Official
- reference-design-contractNo
- lineage-skillNo
Highlighted cells win that row on an objective measure. Rows without a clear winner — category, licence, source — are left unmarked. A higher trust score means better auditability and maintenance, not safer code.