# SigNoz/signoz — health index 88/100 (Excellent)

> Inspection of the public repository SigNoz/signoz by inspect.software. It holds a health index of 88 out of 100, placing it in the Excellent band. The index is a signal derived from publicly visible practice, not a warranty, a security audit, or an endorsement, and it is independent of payment.

- Repository: https://github.com/SigNoz/signoz
- Report page: https://inspect.software/software/SigNoz/signoz
- Full JSON report: https://inspect.software/api/repositories/SigNoz/signoz/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/s/SigNoz/signoz.svg
- Inspected: 2026-07-18
- Methodology: metrics 1.13.0, report schema 0.12.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 96/100 | Excellent |
| Community & Adoption | 18% | 92/100 | Excellent |
| Sustainability & Governance | 24% | 88/100 | Excellent |
| Engineering Quality | 20% | 94/100 | Excellent |
| Security | 16% | 63/100 | Moderate |
| AI Readiness | not counted | 79/100 | Good |

## Repository facts

| Field | Value |
|---|---|
| Description | SigNoz is an open-source, OpenTelemetry-native observability platform for your team and their AI agents. Get logs, metrics, and traces in one tool with features like APM, distributed tracing, log management, infra monitoring, etc. Combined with SigNoz MCP and a native AI teammate (in SigNoz Cloud) it helps you build more resilient apps. |
| Homepage | https://signoz.io |
| Primary language | TypeScript |
| Stars | 30,364 |
| Forks | 2,344 |
| Created | 2021-01-03 |
| Last push | 2026-07-18 |
| Latest release | v0.133.0 |
| Commits (last year) | 1,754 |
| Bus factor | 8 |
| Topics | observability, application-monitoring, opentelemetry, distributed-tracing, apm, go, monitoring, react, self-hosted, typescript, logs, metrics, open-source, tracing, reactjs, nextjs, jaeger, log, prometheus, good-first-issue |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | frontend | 2.0.0-alpha.4 | 2,489 |
| go | github.com/SigNoz/signoz | v0.133.0 | — |

## Vitality — 96/100 (Excellent)

Is the project alive — is code being written and are releases shipping? Weight: 22% of the overall index.

### Development activity — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 0 days ago |
| Commit cadence | met | 36 / 36 | 52/52 weeks with commits |
| Commit volume | met | 18 / 18 | 1754 commits in the last year |
| OpenSSF Scorecard: Maintained | met | 10 / 10 | 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10 |

### Release discipline — 90/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 100 releases published |
| Release recency | met | 36 / 36 | latest release 2 days ago |
| Release cadence | met | 27 / 27 | a release every ~2.4 days |
| OpenSSF Scorecard: Signed-Releases | not met | 0 / 10 | Project has not signed or included provenance with any releases. |

### Abandonment — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | maintenance record not established from the collected data |

## Community & Adoption — 92/100 (Excellent)

Does the project have users, downloads, attention, and a welcoming setup for contributors? Weight: 18% of the overall index.

### Popularity & adoption — 97/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | met | 60 / 60 | 30,364 stars |
| Forks | met | 25 / 25 | 2,344 forks |
| Watchers | partial | 11.8 / 15 | 132 watchers |

### Community health — 86/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | partial | 16.9 / 22.5 | license file present, not a recognized license |
| CONTRIBUTING guide | met | 18 / 18 | — |
| Code of conduct | met | 13.5 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | met | 6.3 / 6.3 | — |

## Sustainability & Governance — 88/100 (Excellent)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 24% of the overall index.

### Maintainer resilience (bus factor) — 98/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | met | 54 / 54 | 8 contributor(s) cover half of all commits |
| Commit distribution | partial | 20.6 / 22.5 | top contributor authored 8% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 100 contributors |
| OpenSSF Scorecard: Contributors | met | 10 / 10 | project has 21 contributing companies or organizations |

### Issue & PR responsiveness — 80/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 33.5 / 46.8 | 72% of issues closed |
| PR acceptance | partial | 31.1 / 38.2 | 5763/7078 decided PRs merged |
| OpenSSF Scorecard: Code-Review | met | 15 / 15 | all changesets reviewed |

### Ownership & stewardship — 74/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 20.3 / 25 | 668 followers of SigNoz |
| Track record | partial | 24.1 / 25 | 155 public repos, account ~5 yr old |

### Package maintenance — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Published & resolvable | met | 25 / 25 | 1 package(s) on go |
| Publish recency | met | 35 / 35 | latest publish 2 days ago |
| Version history | met | 20 / 20 | 703 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

## Engineering Quality — 94/100 (Excellent)

Are baseline engineering and documentation practices in place? Weight: 20% of the overall index.

### Engineering practices — 90/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 17 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | .golangci.yml |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | met | 6.4 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | met | 20 / 20 | 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |

### Documentation — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | met | 25 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://signoz.io |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 20 topics |
| Wiki | met | 10 / 10 | — |

## Security — 63/100 (Moderate)

Are visible security and supply-chain practices strong, with no malicious dependency and no unresolved high-risk jurisdiction exposure? Weight: 16% of the overall index.

### Security posture — 63/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | partial | 6 / 7.5 | branch protection is not maximal on development and all release branches |
| CI-Tests | met | 2.5 / 2.5 | 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | met | 7.5 / 7.5 | all changesets reviewed |
| Contributors | met | 2.5 / 2.5 | project has 21 contributing companies or organizations |
| Dangerous-Workflow | met | 10 / 10 | no dangerous workflow patterns detected |
| Dependency-Update-Tool | met | 7.5 / 7.5 | update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | partial | 2.2 / 2.5 | license file detected |
| Maintained | met | 7.5 / 7.5 | 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | met | 5 / 5 | packaging workflow detected |
| Pinned-Dependencies | not met | 0 / 5 | dependency not pinned by hash detected -- score normalized to 0 |
| SAST | not met | 0 / 5 | SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | met | 5 / 5 | security policy file detected |
| Signed-Releases | not met | 0 / 7.5 | Project has not signed or included provenance with any releases. |
| Token-Permissions | not met | 0 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | partial | 3 / 7.5 | 6 existing vulnerabilities detected |

### High-Risk Jurisdiction Exposure — 100/100 (Excellent)

Only high-confidence self-published location evidence affects this multiplier. Ambiguous matches are review-only; country evidence is not proof of nationality, citizenship, legal registration, malicious intent, or sanctions status.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Policy exposure multiplier | met | 100 / 100 | no confirmed policy-scope location match |

## AI Readiness — 79/100 (Good)

How well is the repo equipped to be developed and maintained with AI coding agents? An independent, experimental badge — weight 0.0, so it is surfaced on its own and does not affect the overall health score.

### Agent context & guidance — 75/100 (Good)

Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | met | 45 / 45 | frontend/AGENTS.md, frontend/CLAUDE.md |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | excluded | 0 / 40 | no data |

### Verify loop (build / test / typecheck) — 88/100 (Excellent)

Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | met | 18 / 18 | Makefile |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | .golangci.yml |
| Static type checking | met | 11 / 11 | frontend/tsconfig.json, tests/e2e/tsconfig.json |
| Reproducible environment | met | 10 / 10 | Dockerfile, lockfile |
| Demonstrated agent practice | excluded | 0 / 10 | no data |
| Automated maintenance | excluded | 0 / 8 | no data |
| OpenSSF Scorecard: Pinned-Dependencies | not met | 0 / 10 | dependency not pinned by hash detected -- score normalized to 0 |

### Code legibility for models — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | TypeScript (statically typed) |
| Manageable file sizes | partial | 54.8 / 55 | 26/5800 source files over 60KB |

### Machine-readable interfaces — 40/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| API schema (OpenAPI/GraphQL/proto) | met | 40 / 40 | docs/api/openapi.yml |
| MCP server | not met | 0 / 20 | — |
| Runnable examples | not met | 0 / 40 | — |

## Collection warnings

- npm package 'frontend' points at a different repository (git+https://github.com/danieljackson1983/frontend.git); excluded from ecosystem scoring
- Could not fetch pypi package 'tests' from its registry
- Resolved dependency list truncated to 2000 of 2428 packages (counts remain complete)

## What this report is

inspect.software measures public repositories against a single published, versioned methodology and reports the result as a 1–100 health index. Findings are signals derived from what is visible in public repository data — they are not a security audit, a warranty, or an endorsement, and no result depends on payment.

- Methodology, formulas and weights: https://inspect.software/methodology.md
- What a result does and does not claim: https://inspect.software/wiki/signals-not-warranties.md
- Rating bands: https://inspect.software/wiki/scoring-bands.md
- Corrections: https://inspect.software/contact.md
- Index of all documents: https://inspect.software/llms.txt