Some interest. A stronger README and CI would help.
Importer for native DAZ files (.duf, .dsf)
Documentation
19
README is present.
No install instructions found in the README (−45 pts).
→ Add a section showing how to install dependencies.
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
Licensed under Other.
Engineering
0
No tests detected anywhere in the repository.
→ Add automated tests. They prove the code works and give contributors confidence to make changes.
No CI configuration detected in this repository.
→ If your CI lives elsewhere (a private repo that builds this one) or this project is itself a CI/CD tool, mark this check Not Applicable. Otherwise add a GitHub Actions workflow that runs tests on each push. It takes 15 minutes and reassures contributors their changes won't break things.
No linter or formatter config found.
→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.
No dependency lockfile found (−70 pts).
→ Commit poetry.lock, uv.lock, pdm.lock, Pipfile.lock, conda-lock.yml, or another lockfile for your Python dependency manager.
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Project health
59
No dependency manifest detected at root.
→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.
No .gitignore found (−60 pts).
→ Add a .gitignore to keep build output, node_modules, and secrets out of version control.
Repository has a description.
Actively maintained (pushed within the last month).
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 7Forks
- 0Releases
Community
- 42% - WeakCommunity health
- 1 bus factorlowauthor own >50% of commits
- 83Watchers
Responsiveness
- 1hMedian issue response
- 4d 4hMedian PR merge time
- 8Open issues
Repository files97 root entries
- data
- export_tools
- facs_tools
- hair_tools
- hd_tools
- material_tools
- mesh_tools
- mhx_tools
- morph_tools
- object_tools
- pose_tools
- rig_tools
- rigify_tools
- runtime
- shell_tools
- simple_ik_tools
- simulation_tools
- to_daz_studio
- visibility_tools
- __init__.py
- .gitattributes
- animation.py
- api.py
- apply.py
- asset.py
- baked.py
- blender_manifest.toml
- bone_chains.py
- bone_data.py
- bone.py
- brick.py
- buildnumber.py
- camera.py
- cgroup.py
- channels.py
- convert.py
- cycles.py
- daz.py
- dbzfile.py
- debug.py
- dforce.py
- driver.py
- empties.py
- erc.py
- error.py
- figure.py
- files.py
- fileutils.py
- finger.py
- fix.py
- formula.py
- framer.py
- geometry.py
- geonodes.py
- guess.py
- hair_material.py
- hd_data.py
- LICENSEGood: Licensed under Other.
- lie.py
- light.py
- load_json.py
- load_morph.py
- localtex.py
- locks.py
- main.py
- material.py
- matsel.py
- merge_grafts.py
- merge_materials.py
- merge_rigs.py
- merge_uvs.py
- modifier.py
- morphing.py
- neighbor.py
- node.py
- panel.py
- pbr.py
- pin.py
- propgroups.py
- proxy.py
- README.mdGood: README is present.Issue: README is very short (−20 pts). 400+ characters earns +10 pts; 1,500+ earns +20 pts.Fix: Add an Overview, Install, Usage, and Contributing section at minimum.Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Issue: No live demo link in the README (−20 pts).Fix: Link to a deployed version, docs site, or demo video. Users want to see it running.Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
- render.py
- rig_utils.py
- scan.py
- selector.py
- settings.py
- slider.py
- store.py
- tables.py
- toon.py
- transfer.py
- transform.py
- tree.py
- uilist.py
- utils.py
- visibility.py
- winder.py