guardian/live-corona-data-vaccine-page
Logical Components
An overview of source code logical components.

Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure at level 1 (relative to the source code root).

Bubble Chart | Tree Map
Component Sizes (Lines of Code)
The "primary" logical decomposition has 11 components.

Archive6655 LOC (56%) 77 files
state_by_state1207 LOC (10%) 13 files
ROOT1176 LOC (9%) 16 files
state_outbreaks764 LOC (6%) 15 files
weekly521 LOC (4%) 12 files
new_thrashers455 LOC (3%) 10 files
booster_feed303 LOC (2%) 8 files
vaccine_availability259 LOC (2%) 8 files
indigenous189 LOC (1%) 3 files
cases_and_hospo178 LOC (1%) 3 files
modules156 LOC (1%) 6 files

scope details...
  • 171 files, 11,863 LOC (100.0% vs. main code).
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
ROOT93 commits (32%)
state_by_state46 commits (16%)
Archive20 commits (6%)
booster_feed20 commits (6%)
vaccine_availability19 commits (6%)
state_outbreaks18 commits (6%)
modules15 commits (5%)
new_thrashers14 commits (4%)
cases_and_hospo11 commits (3%)
indigenous8 commits (2%)
weekly7 commits (2%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2026 2025 2024 2023 2022 2021
Archive
11
9
ROOT
44
49
indigenous
3
5
state_by_state
15
31
vaccine_availability
2
17
cases_and_hospo
4
7
booster_feed
14
6
state_outbreaks
8
10
weekly
1
2
4
modules
1
14
new_thrashers
12
2


Dependencies between components in same commits (past 180 days)
The number on the lines shows the number of shared commits.
See detailed temporal dependencies report...

No temporal dependencies found.

About This Analysis

Logical decomposition is a representation of the organization of the main source code, where every and each file is put in exactly one logical component.

  • A software system can have one or more logical decompositions.
  • A logical decomposition can be defined in two ways in Sokrates.
  • First approach is based on the folders structure. Components are mapped to folders at defined folder depth relative to the source code root.
  • Second approach is based on explicit definition of each component. In such explicit definitions, components are explicitly named and their files are selected based on explicitly defined path and content filters.
  • A logical decomposition is considered invalid if a file is selected into two or more components. This constraint is introduced in order to facilitate measuring of dependencies among components.
  • Files not assigned to any component are put into a special "Unclassified" component.

2026-10-07 12:45