# calcom/cal.diy — health index 19/100 (Critical)

> Inspection of the public repository calcom/cal.diy by inspect.software. It holds a health index of 19 out of 100, placing it in the Critical 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/calcom/cal.diy
- Report page: https://inspect.software/software/calcom/cal.diy
- Full JSON report: https://inspect.software/api/repositories/calcom/cal.diy/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/c/calcom/cal.diy.svg
- Inspected: 2026-09-15
- Methodology: metrics 2.10.0, report schema 0.34.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 89/100 | Excellent |
| Community & Adoption | 17% | 95/100 | Exceptional |
| Sustainability & Governance | 23% | 90/100 | Excellent |
| Engineering Quality | 19% | 90/100 | Excellent |
| Security | 16% | 18/100 | Critical |
| AI Readiness | 4% | 83/100 | Excellent |

The weighted overall 79 is calibrated to 93 on the published index scale (record calibration 2026-08-02). A dependency reported as a malicious package applies a 35% multiplier to weighted overall health and gives it a Critical ceiling of 19.

## Repository facts

| Field | Value |
|---|---|
| Description | Scheduling infrastructure for absolutely everyone. |
| Classification | network-service, web-ui, cli, tui |
| Homepage | https://cal.diy |
| Primary language | TypeScript |
| License | MIT |
| Stars | 48,475 |
| Forks | 15,129 |
| Created | 2021-03-22 |
| Last push | 2026-09-14 |
| Latest release | v6.2.0 |
| Commits (last year) | 2,322 |
| Bus factor | 8 |
| Topics | open-source, typescript, nextjs, next-auth, postgresql, prisma, t3-stack, tailwindcss, trpc, turborepo, zod |

## Vitality — 89/100 (Excellent)

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

### Development activity — 96/100 (Exceptional)

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

### Release discipline — 78/100 (Good)

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 100 releases published |
| Release recency | partial | 16.2 / 36 | latest release 197 days ago |
| Release cadence | met | 27 / 27 | a release every ~3.5 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### Abandonment — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | last human commit 1 days ago |

## Community & Adoption — 95/100 (Exceptional)

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

### Popularity & adoption — 98/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | met | 60 / 60 | 48,475 stars |
| Forks | met | 25 / 25 | 15,129 forks |
| Watchers | partial | 12.9 / 15 | 213 watchers |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (MIT) |
| 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 — 90/100 (Excellent)

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

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 37 / 42 | 88% of issues closed |
| PR acceptance | partial | 20.4 / 30 | 13111/19322 decided PRs merged |
| Newcomer PR acceptance | partial | 0.5 / 13 | 1/26 first-time contributors' PRs merged in 30d |
| OpenSSF Scorecard: Code-Review | met | 15 / 15 | all changesets reviewed |

### Ownership & stewardship — 97/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | met | 20 / 20 | — |
| Owner reach | partial | 24 / 25 | 2,150 followers of calcom |
| Track record | partial | 23.1 / 25 | 43 public repos, account ~5 yr old |

## Engineering Quality — 90/100 (Excellent)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 50 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | biome.json |
| 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 — 90/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | met | 25 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://cal.diy |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 11 topics |
| Wiki | not met | 0 / 10 | — |

## Security — 18/100 (Critical)

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 — 18/100 (Critical)

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized. A dependency reported as a malicious package applies a 35% multiplier to Security posture and gives it a Critical ceiling of 19.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | partial | 3.8 / 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 14 contributing companies or organizations |
| Dangerous-Workflow | not met | 0 / 10 | 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 | met | 2.5 / 2.5 | license file detected |
| Maintained | met | 7.5 / 7.5 | 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | excluded | 0 / 5 | packaging workflow not 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 | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | not met | 0 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | not met | 0 / 7.5 | 256 existing vulnerabilities detected |

### Dependency advisories — 20/100 (At Risk)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 2982 resolved dependencies against OSV; 854 could not be assessed (no resolved version, an unsupported ecosystem, or beyond the reported package list). This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Direct dependencies free of known advisories | partial | 2 / 35 | 18 affected: next 15.5.15 (critical 9.8), next 16.2.3 (critical 9.8), next-auth 4.24.13 (critical 9.1), +15 more |
| Indirect dependencies free of known advisories | excluded | 0 / 25 | transitive set not separable from development and test dependencies in this scope |
| No advisories left outstanding | partial | 12.8 / 40 | 13 advisory-carrying package(s) unaddressed past 90 days; oldest published 710 days ago |

### Malicious dependencies — 35/100 (Weak)

1 resolved dependency(ies) resolve to a version the registry still serves and the OpenSSF corpus reports as malicious. Direct and indirect are treated alike: an install-time payload runs at any depth in the graph. A report here concerns the package as published, not the maintainers of this repository, which may have resolved it unknowingly.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| No dependency reported as a malicious package | partial | 35 / 100 | 1 reported as malicious: http 0.0.1-security |

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

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 — 83/100 (Excellent)

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight: agent tooling is a real maintenance signal, but its absence must never gate the top of the scale (calibration saturates at raw 91, so 100/100 remains reachable with AI Readiness at zero).

### Agent context & guidance — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | met | 45 / 45 | .opencode/skill/vercel-react-best-practices/AGENTS.md, AGENTS.md, CLAUDE.md, agents/skills/vercel-react-best-practices/AGENTS.md, specs/_templates/AGENTS.md, specs/_templates/CLAUDE.md, specs/cancellation-reason-requirement/CLAUDE.md |
| Machine-readable docs (llms.txt) | met | 15 / 15 | llms.txt served by the project website (https://docs.railway.app/llms.txt) |
| Legible commit history | met | 40 / 40 | 100 of 100 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 64/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | biome.json |
| Static type checking | met | 11 / 11 | apps/api/v2/tsconfig.json, apps/docs/tsconfig.json, apps/web/tsconfig.json, example-apps/credential-sync/tsconfig.json, packages/app-store-cli/tsconfig.json, packages/app-store/tsconfig.json, packages/coss-ui/tsconfig.json, packages/dayjs/tsconfig.json, packages/debugging/tsconfig.json, packages/emails/tsconfig.json, packages/embeds/embed-core/tsconfig.json, packages/embeds/embed-react/test/packaged/tsconfig.json, packages/embeds/embed-react/tsconfig.json, packages/embeds/embed-snippet/tsconfig.json, packages/features/auth/tsconfig.json, packages/features/tsconfig.json, packages/lib/tsconfig.json, packages/platform/atoms/tsconfig.json, packages/platform/constants/tsconfig.json, packages/platform/enums/tsconfig.json, packages/platform/examples/base/tsconfig.json, packages/platform/libraries/tsconfig.json, packages/platform/types/tsconfig.json, packages/platform/utils/tsconfig.json, packages/testing/tsconfig.json, packages/trpc/tsconfig.json, packages/types/tsconfig.json, packages/ui/tsconfig.json |
| Reproducible environment | met | 10 / 10 | Dockerfile, lockfile |
| Demonstrated agent practice | met | 10 / 10 | 7 of the last 100 commits agent-authored or agent-credited |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | not met | 0 / 10 | dependency not pinned by hash detected -- score normalized to 0 |

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

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

### Machine-readable interfaces — 80/100 (Excellent)

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

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- First-time contributor figures cover 12 of 32 authors (cap 12)
- Resolved dependency list truncated to 3000 of 3836 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