# code996

统计 Git 项目的 commit 时间分布，进而推导出项目的编码工作强度。  Analyzes the commit time distribution of Git projects to infer coding work intensity.

Repository: https://github.com/hellodigua/code996
Canonical: https://ross.abutalabs.com/products/code996
Homepage: https://hellodigua.github.io/code996/
Language: TypeScript
License: MIT
License Family: permissive
Last push: 2026-07-31T10:40:06+00:00
Link (homepage): https://hellodigua.github.io/code996/

## Health v2 (maintenance only)
Score: 80/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 95, release rhythm 95, longevity 21
- inputs: {"age_days": 301, "days_push": 33, "days_rel": 33, "gap_med": 10.0, "n_releases_24m": 7}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2086, forks 79 (observed 2026-08-28T04:06:11.943840+00:00)

## What it is
code996 is a Node.js CLI tool that analyzes Git commit time distributions to infer a project's coding work intensity and overtime culture. It runs fully offline via `npx -y code996`, producing terminal reports plus local bilingual HTML visualizations including a '996 index', monthly trends, and multi-repo comparisons.

## Use cases
- analyze overtime culture of a git repository
- check if a company has 996 work schedule before joining
- measure team coding work intensity from commit times
- compare workload across multiple git repos
- track monthly overtime trends in a project
- generate a work-hours report from git log
- detect weekend and late-night commit patterns

## When to choose
- you want a quick, privacy-safe, fully local analysis of commit time patterns
- you're evaluating a new team's real working hours before or after joining
- you need multi-repo overtime comparisons with visual HTML reports
- you work with Chinese holiday/调休 schedules and need accurate workday filtering

## When to avoid
- you need code quality or productivity metrics beyond commit timestamps
- your workflow uses squash merges or rebases that obscure true commit times
- you need server-side or CI-integrated analytics rather than a local CLI
- commit timestamps are unreliable in your repos (e.g., cherry-picked or imported history)

## Facets
- artifact type: cli-tool
- maturity: active
- function: analytics, developer-tools, cli, data-visualization
- domain: developer-tools, analytics, hr
- platform: cli, cross-platform
- tags: git-analysis, work-intensity, overtime-detection, 996, commit-time-distribution, team-culture, offline-analysis, privacy, command-line, nodejs

## Member repositories
- hellodigua/code996 (main) score 80
- hellodigua/code996-web (frontend) score 10

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:11.943840+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:55:47.310522+00:00, confidence not recorded.
  - readme: https://github.com/hellodigua/code996 (fetched 2026-08-28T04:06:11.943840+00:00, sha a16026874887)
  - homepage: https://hellodigua.github.io/code996/ (fetched 2026-08-29T10:36:22.724482+00:00, sha 0b9e55101641)
  - registry_npm: https://registry.npmjs.org/code996 (fetched 2026-08-29T10:36:22.733505+00:00, sha 6335078e0de3)
- Data as of 2026-08-30T08:39:29.467469+00:00.