lengstrom/fast-style-transfer vs sjmoran/deeplpf-image-enhancement
Both showing Concerns signals — pick on fit, not health
As of June 2026, fast-style-transfer and deeplpf-image-enhancement both show concerning maintenance signals. fast-style-transfer last saw a commit 2 years ago with 16+ active contributors, while deeplpf-image-enhancement last saw a commit 1 year ago with 4+ active contributors. Neither has known critical or high-severity CVEs in its dependency tree.
Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.
lengstrom/fast-style-transfer →
Stale and unlicensed — last commit 3y ago
no license — legally unclear; last commit was 3y ago…
no license — can't legally use code; no tests detected…
Documented and popular — useful reference codebase to read through.
no license — can't legally use code; last commit was 3y ago…
- ⚠Stale — last commit 3y ago
- ⚠Concentrated ownership — top contributor handles 54% of recent commits
- ⚠No license — legally unclear to depend on
- ⚠No CI workflows detected
- ⚠No test directory detected
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓16 active contributors
What would improve this?
- →Use as dependency Concerns → Mixed if: publish a permissive license (MIT, Apache-2.0, etc.)
- →Fork & modify Concerns → Mixed if: add a LICENSE file
- →Deploy as-is Concerns → Mixed if: add a LICENSE file
Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests + OpenSSF Scorecard
sjmoran/deeplpf-image-enhancement →
Stale and unlicensed — last commit 2y ago
no license — legally unclear; last commit was 2y ago…
no license — can't legally use code; no tests detected…
Documented and popular — useful reference codebase to read through.
no license — can't legally use code; last commit was 2y ago…
- ⚠Stale — last commit 2y ago
- ⚠Small team — 4 contributors active in recent commits
- ⚠Concentrated ownership — top contributor handles 64% of recent commits
- ⚠No license — legally unclear to depend on
- ⚠No CI workflows detected
- ⚠No test directory detected
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓4 active contributors
What would improve this?
- →Use as dependency Concerns → Mixed if: publish a permissive license (MIT, Apache-2.0, etc.)
- →Fork & modify Concerns → Mixed if: add a LICENSE file
- →Deploy as-is Concerns → Mixed if: add a LICENSE file
Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests + OpenSSF Scorecard
Signal-by-signal breakdown
| fast-style-transfer | deeplpf-image-enhancement | |
|---|---|---|
| Stars | 10,971 | 257 |
| Last commit | 2y ago | 1y ago |
| License | — | — |
| Open issues | 112 | 1 |
| Has tests | — | — |
| Has CI | — | — |
| Test coverage | 0% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Concerns signals | Concerns signals |
Want the full analysis? lengstrom/fast-style-transfer · sjmoran/deeplpf-image-enhancement
Ask AI about lengstrom/fast-style-transfer vs sjmoran/deeplpf-image-enhancement
Open the chat with a comparison question pre-filled.