Good shape overall. A few tweaks would push it into the top tier.

Deep Learning Streamer (DL Streamer) Pipeline Framework is an open-source streaming media analytics framework, based on GStreamer* multimedia framework, for creating complex media analytics pipelines for the Cloud or at the Edge.

Documentation

87

README12pt75

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt93

Contributing guide is detailed and thorough.

License6pt100

Licensed under MIT.

Engineering

71

Linting and formatting5pt0

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.

CI/CD14pt68

CI is configured (.github/workflows/dls-build-and-test-deb_pkgs-and-deb_imgs.yaml).

Tests18pt80

Test files detected (tests).

Reproducibility6pt82

Lockfile present (requirements.txt). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (requirements.txt).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 195
    Forks
  • 46
    Releaseslatest 6y ago

Community

  • Community health
  • authors own >50% of commits
  • 614
    Watchers

Responsiveness

  • 5h
    Median issue response
  • 1h
    Median PR merge time
  • 22
    Open issues
Repository files33 root entries
  • .github
    Good: CI is configured (.github/workflows/dls-build-and-test-deb_pkgs-and-deb_imgs.yaml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • cmake
  • dependencies
  • docker
  • docs
  • girs
  • include
  • python
  • samples
  • scripts
  • SPECS
  • src
  • tests
    Good: Test files detected (tests).
  • thirdparty
  • .clang-format
  • .dockerignore
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .yamllint
  • CMakeLists.txt
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CODESTYLE.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • intro.gif
  • LICENSE
    Good: Licensed under MIT.
  • Makefile
  • pylintrc
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (requirements.txt).
  • SECURITY.md
    Good: Security policy present.
  • third-party-programs.txt
  • vcpkg-configuration.json
  • vcpkg.json