| name | engineering-package-evaluator |
| version | 1.0.0 |
| updated | "2026-02-26T00:00:00.000Z" |
| category | development |
| description | Reusable evaluation framework for assessing Python engineering packages
for adoption — license compatibility, maintenance health, integration
risk, and dependency strategy.
|
| tags | ["package","evaluation","license","dependency","python"] |
| platforms | ["linux","macos","windows"] |
| invocation | engineering-package-evaluator |
| depends_on | [] |
| requires | [] |
| see_also | ["plugin-management"] |
Engineering Package Evaluator Skill
Structured evaluation framework for Python engineering packages being
considered for adoption into digitalmodel or other MIT-licensed projects.
When to Use This Skill
- Evaluating a new Python package for integration
- Assessing license compatibility for a dependency
- Reviewing maintenance health of an existing dependency
- Deciding between direct dependency vs optional extra vs wrapper
Evaluation Checklist
1. License Compatibility
Package License?
├── MIT / BSD / Apache-2.0 → Direct dependency (safe)
├── LGPL-2.1 / LGPL-3.0 → Direct dependency (dynamic linking OK)
├── GPL-2.0 / GPL-3.0 → Optional extra ONLY (cannot bundle)
├── AGPL → Do not use (viral, affects SaaS)
└── Proprietary / Unknown → Do not use without legal review
2. Maintenance Health
| Metric | Green | Yellow | Red |
|---|
| Last commit | < 6 months | 6–18 months | > 18 months |
| Last release | < 12 months | 12–24 months | > 24 months |
| Open issues | < 50 | 50–200 | > 200 |
| Response time | < 1 week | 1–4 weeks | > 1 month |
| CI status | Passing | Flaky | Failing/none |
| Python 3.10+ | Supported | Untested | Incompatible |
3. Community & Quality
| Metric | Strong | Moderate | Weak |
|---|
| GitHub stars | > 500 | 100–500 | < 100 |
| Contributors | > 10 | 3–10 | 1–2 |
| Documentation | Comprehensive | Basic | None/stale |
| Test suite | > 80% coverage | Some tests | No tests |
| JOSS/academic paper | Published | Preprint | None |
4. Dependency Risk
