mozilla / releases-comm-central

1319	2902	2862	3006	3281	2889	2980	2499	1881	1658	1587	1738	2179	3262	2594	2504	3434	1731	137
39	54	59	56	70	81	86	90	101	106	133	151	132	204	203	202	216	129	16
2025	2024	2023	2022	2021	2020	2019	2018	2017	2016	2015	2014	2013	2012	2011	2010	2009	2008	2007

	travis github actions circleci npm yarn gradle make docker
Standard analyses:
		Main Code: 931,066 LOC (4097 files) = JS (33%) + MJS (23%) + CPP (16%) + XHTML (7%) + CSS (6%) + H (4%) + XML (2%) + XUL (1%) + FTL (1%) + PY (<1%) + JSM (<1%) + RS (<1%) + RDF (<1%) + NSI (<1%) + IN (<1%) + C (<1%) + NSH (<1%) + HTML (<1%) + YAML (<1%) + MM (<1%) + TOML (<1%) + WXS (<1%) + JINJA2 (<1%) + PRI (<1%) + INC (<1%) Secondary code: Test: 340,589 LOC (2257); Generated: 46 LOC (1); Build & Deploy: 687 LOC (23); Other: 71,777 LOC (1183);
		File Size: 37% long (>1000 LOC), 19% short (<= 200 LOC)
		Logical Component Decomposition: primary (12 components)
		18 years, 1 month old 93% of code older than 365 days 28% of code not updated in the past 365 days
		21% of code updated more than 50 times Also see temporal dependencies for files frequently changed in same commits.
		Goals: Keep the system simple and easy to change (4)
Experimental analyses (less reliable heuristic analyses):
		Unit Size: 13% long (>100 LOC), 39% short (<= 10 LOC)
		Conditional Complexity: 11% complex (McCabe index > 50), 47% simple (McCabe index <= 5)
		Static Component Dependencies: primary (12 components)

	Features of interest: TODOs 345 files

All Analysis Reports

Source Code Overview

Components

Temporal Dependencies

Duplication

File Size

File Age & Freshness

File Change Frequency

Commits

Contributors

Unit Size*

Conditional Complexity*

Features of Interest

All Metrics

Goals & Controls

Component Dependencies*

Trend

Notes & Findings

Overall Activity Per Year

Latest commit date: 2025-05-11

Reference analysis date: 2025-05-11

339

commits
(30 days)

22

contributors
(30 days)

1319	2902	2862	3006	3281	2889	2980	2499	1881	1658	1587	1738	2179	3262	2594	2504	3434	1731	137
39	54	59	56	70	81	86	90	101	106	133	151	132	204	203	202	216	129	16
2025	2024	2023	2022	2021	2020	2019	2018	2017	2016	2015	2014	2013	2012	2011	2010	2009	2008	2007

Activity Per File Extension

commits

	2025	2024	2023	2022	2021	2020	2019	2018	2017	2016	2015	2014	2013	2012	2011	2010	2009	2008	2007
	523	1206	1462	1578	1647	1457	1605	1062	641	702	707	781	989	1511	1210	1050	1599	796	67	js
mjs	320	691	298	101																mjs
	304	392	278	343	502	402	436	433	429	264	224	221	255	478	399	391	655	311	2	cpp
	88	274	527	545	570	357	418	389	216	172	151	168	198	315	333	248	438	121	25	css
	104	255	9	8	5	11	3	13	4											toml
	103	222	427	527	494	459	45	29	27	34	16	29	40	56	41	82	107	28	4	xhtml
	75	240	3																	rs
	151	164	92	130	165	171	158	160	109	87	82	73	104	145	131	140	231	120	2	h
	50	228	210	225	161	171	197	172	31											yaml
in	46	176	65	51	78	98	87	110	138	139	137	207	254	344	313	591	401	224	1	in
	13	157	192	124	53	60	60	41	24	11	23	22	19	27	44	70	42	31		py
	44	117	161	240	165	99	20	9												ftl
jsm		93	445	871	866	711	346	223	122	140	175	191	229	323	126	58	127	20		jsm
xul	18	8	7	16	57	65	557	313	129	199	160	186	185	366	412	302	573	310	41	xul
	11	14	23	14	23	22	20	15	8	5	8	11	23	46	32	24	23	3	2	html
	5	17	13	10	26	44	236	356	182	211	144	221	276	459	287	198	429	167	67	xml
	3	8	7	9	14	23	24	2		9	7	5	1	3	7	8	3	9		c
nsh	3	5	7	6	5	4	7	3	13	6	1	7	2	9	6	6	18	9		nsh
	1	5	1	4	13	17	12	5	14	7	2	7	15	15	9	8	9	9		mm
	2		2		2	1	1	46		1		3	1	3	1	10	15	17		inc
jinja2		2	4																	jinja2
nsi		1	13	7	8	10	3	9	14	8	3	8	5	14	15	23	20	24		nsi
	1			1	5	8	7	13	9	13	7	9	15	18	14	35	36	23	2	rdf
pri				2																pri
wxs						1	1	1												wxs

contributors

	2025	2024	2023	2022	2021	2020	2019	2018	2017	2016	2015	2014	2013	2012	2011	2010	2009	2008	2007
	21	37	45	41	50	55	59	55	62	64	91	92	80	136	118	129	151	86	9	js
mjs	24	31	20	10																mjs
	13	27	30	23	35	33	34	34	39	37	39	60	53	81	68	75	80	51	2	cpp
	12	23	22	19	19	18	20	23	16	24	27	27	32	42	38	36	44	30	2	h
	12	21	23	21	19	25	22	26	18	21	23	30	33	42	42	52	58	38	3	css
	14	18	29	27	27	31	12	9	11	12	7	12	9	18	17	25	28	11	3	xhtml
	14	18	11	8	8	10	9	6	1											yaml
	13	18	19	18	17	13	5	3												ftl
in	11	19	12	9	11	13	14	14	18	21	28	40	43	62	53	62	56	46	1	in
	14	15	4	3	2	3	2	8	3											toml
	7	16	13	8	9	7	9	10	6	8	11	13	12	13	13	15	12	11		py
	6	14	3																	rs
jsm		15	30	30	39	42	30	21	30	26	34	36	20	33	19	11	22	7		jsm
	6	9	7	5	8	7	6	7	5	4	5	7	10	18	13	10	9	2	2	html
	3	10	6	9	10	6	24	23	27	24	33	45	36	60	42	38	59	35	9	xml
nsh	3	4	4	4	4	3	4	2	2	4	1	5	1	8	4	4	4	4		nsh
xul	2	3	5	4	6	6	33	28	34	37	42	41	37	59	62	73	79	64	8	xul
	1	4	3	4	5	6	7	2		7	5	4	1	3	3	4	2	3		c
	1	4	1	3	6	6	4	2	6	5	2	7	10	14	6	6	4	3		mm
	1		2		1	1	1	10		1		3	1	2	1	6	7	6		inc
jinja2		1	2																	jinja2
nsi		1	5	4	5	7	1	5	2	3	3	6	5	11	11	10	9	8		nsi
	1			1	2	4	3	7	6	8	5	6	2	9	7	12	13	14	2	rdf
pri				2																pri
wxs						1	1	1												wxs

Visual Code Explorers

MAIN (4097)	Circles	Sunburst
TEST (2257)	Circles	Sunburst
BUILD AND DEPLOYMENT (23)	Circles	Sunburst
GENERATED (1)	Circles	Sunburst
OTHER (1183)	Circles	Sunburst

File Visualizations

File size views:

File age views:

	files grouped by age category files grouped by folder
	files grouped by freshness category files grouped by folder

File change frequency views:

Contributors per file views:

Contributor Visualizations

Contributor dependency views:

past 30 days: graphviz | 2D graph | 2D graph (with files) | 2D graph (with shared files only) | 3D graph | 3D graph (with files) | 3D graph (with shared files only)
past 3 months: graphviz | 2D graph | 2D graph (with files) | 2D graph (with shared files only) | 3D graph | 3D graph (with files) | 3D graph (with shared files only)
past 6 months: graphviz | 2D graph | 2D graph (with files) | 2D graph (with shared files only) | 3D graph | 3D graph (with files) | 3D graph (with shared files only)
past year: graphviz | 2D graph | 2D graph (with files) | 2D graph (with shared files only) | 3D graph | 3D graph (with files) | 3D graph (with shared files only)

Components and Dependencies Visualizations

Components

Temporal Dependencies

Duplication

Commits Racing Charts

30 days

3 months

6 months

PRIMARY (12)

Bubble Chart

Tree Map

graphviz

2D

3D

graphviz

2D

3D

graphviz

2D

3D

Duplication Graph

All Time

12 Months

File Dependencies Visualizations

Temporal dependencies among files:

past 30 days: graphviz | 2D graph | 2D graph (with commits) | 3D graph | 3D graph (with commits)
past 3 months: graphviz | 2D graph | 2D graph (with commits) | 3D graph | 3D graph (with commits)
past 6 months: graphviz | 2D graph | 2D graph (with commits) | 3D graph | 3D graph (with commits)

Units Visualizations

Unit size and conditional complexity views:

Lists of Files Per Scope

Analysis Results

CONFIGURATION: JSON
ALL ANALYSIS RESULTS: JSON
DUPLICATES: TXT | JSON
UNITS: TXT | JSON
CONTRIBUTORS: TXT | JSON
LOGICAL DECOMPOSITIONS: JSON
CONCERNS: JSON
CONTROLS: TXT
ALL METRICS: TXT

Zipped Files

GIT HISTORY: ZIP
ALL FILES IN ALL ANALYSIS SCOPES: ZIP

Generative AI tools, like ChatGPT or Gemini, can help you explore and discuss various aspects of source code repositories using simple prompts and file uploads. Sokrates provides you with curated data that you can use to analyze your source code further.

Example Prompt 1: Repository Evolution Analyzer (based on git history)

Try on: OpenAI ChatGPT | Claude.ai Chat | Google Gemini

Files to upload: git-history.zip

Prompt:

You are an experienced software architect tasked with analyzing Git commit history.
Context:
- Repository Name: mozilla / releases-comm-central
- Repository Description: EXPERIMENTAL - copy of comm-central for forking on github
- Data Provided: A plain text file containing Git commit records. Source code is not available.
- Analysis Basis: Your analysis must be based solely on inferring context from the provided file paths, file names, file extensions, commit timestamps, and author information within the commit records.

Input Format:
The commit records are provided in the following format per line:
[YYYY-MM-DD] [author email] [commit hash] [file path changed]

Requested Insights:

Please analyze the provided commit history and generate a report covering the following sections:

1. Management Summary
- Provide a concise, high-level overview suitable for non-technical stakeholders.
- Summarize the repository's likely purpose, main development phases observed, and key takeaways about the team structure/activity.

2. Functional Overview
- Based only on file/module/class names, infer and describe the primary functions and capabilities of the software in this repository.
- What services or features does the codebase seem to support?

3. Key Business/Domain Concepts
- Identify and list core business or domain concepts reflected in the file and directory names (e.g., reporting, analytics, data export, user management, sourcecode analysis, landscape, visualization).

4. Inferred Architecture & Design
- Infer potential architectural patterns (e.g., modular, layered, microservices) based on directory structures and file naming conventions.
- Highlight notable design choices evident from the structure, such as separation of concerns (e.g., common module), use of configuration files, or templating engines.

5. Inferred Technology Stack
- List the programming languages, frameworks, libraries, and tools likely used, based on file extensions (.java, .py, .js, .html, .xml, .yml, pom.xml, dockerfile), configuration files, and common directory structures (e.g., /src/main/java).
- Categorize these technologies where possible (e.g., Backend, Frontend, Build, Infrastructure).

6. Logical Components / Modules
- Identify the major logical components or modules suggested by the directory structure (e.g., codeanalyzer, reports, cli, common, web).
- Briefly describe the inferred purpose of each major component.

7. Evolution by Year
- Summarize the apparent focus of development activity for each year present in the commit history.
- Assign a thematic title to each year (e.g., "Year 1: Foundation & Core Analysis", "Year 2: Reporting & Visualization Expansion").

8. Trends Over Time
Identify and describe significant trends observed across the years, such as:
- Shifts in technology usage (e.g., introduction of Docker).
- Changes in module activity (e.g., increased focus on landscape analysis).
- Signs of project maturity, expansion into new areas, or periods of focused maintenance.
9. Team Dynamics
- Analyze contributor patterns based on author emails and commit frequency:
 - Identify core maintainer(s) vs. occasional contributors.
 - Describe observable contribution trends (e.g., stable team, high turnover, reliance on a single developer).
 - Note any appearance of automated contributors (e.g., Dependabot).
10. Risk Analysis:
- Based on the findings in all previous sections (Team Dynamics, Technology, Architecture, Evolution), identify potential key risks for the project.
- Examples: Key person dependency, technology obsolescence, maintainability challenges due to complexity, potential scalability bottlenecks, bus factor.

Input File:
You will receive the commit records in a plain text file. Please parse this file to perform your analysis.

Example Prompt 2: File name conventions

Try on: OpenAI ChatGPT | Claude.ai Chat | Google Gemini

Files to upload: files.json

Prompt:

Example Prompt 3: Technology analyzer (based of file paths)

Try on: OpenAI ChatGPT | Claude.ai Chat | Google Gemini

Files to upload: files.json

Prompt:

Analyze the provided list of file paths to identify as many technologies, frameworks, tools, programming languages, cloud services, and architectural patterns used in the project as possible.

**Input:**
Please analyze the following list of file structures (provided as a list of strings or a JSON object containing file paths and optionally extensions/metadata):

*(Example: A JSON array like the one previously provided, or a simple list like `["src/server.ts", "Dockerfile", "tests/e2e/spec.cy.js", "infra/main.tf"]`)*

**Analysis Instructions:**
When performing the analysis, please consider the following:

1. **File Extensions:** Identify languages and configuration types (e.g., `.ts`, `.js`, `.py`, `.java`, `.tf`, `.yml`, `.hcl`, `.css`, `.html`).
2. **Directory Structure & Naming:** Look for conventional directory names (`src`, `tests`, `infra`, `docs`, `cicd`) and names indicating specific components or frameworks (`packages/bff`, `features`, `controllers`, `services`, `cypress`).
3. **Specific Filenames:** Identify standard configuration or definition files (e.g., `package.json`, `pom.xml`, `docker-compose.yml`, `Dockerfile`, `Jenkinsfile`, `webpack.config.js`, `tsconfig.json`, `requirements.txt`, `terragrunt.hcl`, `lint-staged.config.js`, `commitlint.config.js`).
4. **Keywords in Paths:** Look for names of known technologies, tools, frameworks, or cloud providers within the paths (e.g., `aws`, `azure`, `lambda`, `sqs`, `react`, `nest`, `k6`, `datadog`, `pm2`).

**Output:**
Please present the findings as a list of identified technologies. If possible, group them into relevant categories such as:

* Programming Languages
* Frameworks & Runtimes
* Testing Tools
* Infrastructure as Code / Cloud Providers
* Containerization & Orchestration
* Build Tools / Bundlers
* Databases (if identifiable)
* Monitoring & Logging
* CI/CD & Dev Tools
* Architectural Patterns