Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-31 10:39 UTC

d3 / d3-time

A calculator for humanity’s peculiar conventions of time.

JavaScriptISC★ 238 stars⑂ 54 forkssince Jun 2015View on GitHub ↗

d3/d3-time holds a health index of 41 out of 100, placing it in the Weak band. It scores highest on Community & Adoption (66/100) and lowest on Vitality (17/100). It was last updated 818 days ago. A single contributor accounts for most of its recent work.

overall / 100

Weak

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met

Excellent80-92Strong across the board; minor gaps

Good65-79Healthy; gaps are limited and manageable

Moderate50-64Acceptable with notable gaps; review recommended

Weak35-49Material weaknesses across several areas

At Risk20-34Significant weaknesses; adoption warrants caution

Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 49 is calibrated to 48 on the published index scale (record calibration 2026-08-02).

Ownership

D3Organization

2,001 followers54 public repossince Mar 2012

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	d3-time	3.1.0	304,261,654	38	1367 days ago	d3 d3-module time interval calendar

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

17Critical · 21% of overall

Development activity

1Critical

Abandonment alert

Work has arrived and nobody has attended to it

no human commit in 818 daysautomated commits excludedreleases stalledOpenSSF Scorecard reports it unmaintained

Silence alone is never the finding — a small, finished library may need no commits for years. This alert requires both: no human commit for a long time, and obligations the project is visibly not discharging. Automated commits do not count as maintenance.

How abandonment is assessed

How it's scored

0/36	Push recency — last push 818 days ago
0/36	Commit cadence — 0/52 weeks with commits
0/18	Commit volume — 0 commits in the last year
0/10	OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Inputs used

commits_last_year	0
human_commit_share	0.99
days_since_last_push	818
active_weeks_last_year	0

Release discipline

40Weak

How it's scored

27/27	Ships releases — 36 releases published
0/36	Release recency — latest release 1,367 days ago
12.6/27	Release cadence — a release every ~204.1 days
0/10	OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.

Inputs used

releases_count	36
latest_release_tag	v3.1.0
releases_from_tags	no
days_since_latest_release	1,367
mean_days_between_releases	204.1

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

66Good · 17% of overall

Popularity & adoption

58Moderate

How it's scored

38.5/60	Stars — 238 stars
14.4/25	Forks — 54 forks
4.7/15	Watchers — 8 watchers

Inputs used

forks	54
stars	238
watchers	8
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (ISC)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	0
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	—
has_pull_request_template	no

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 304,261,654 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	d3-time
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	304,261,654
unverified_packages_excluded	—

Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

60Moderate · 23% of overall

Maintainer resilience (bus factor)

32At Risk

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
2/22.5	Commit distribution — top contributor authored 91% of commits
10.8/13.5	Contributor breadth — 8 contributors
10/10	OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations

Inputs used

bus_factor	1
contributors_sampled	8
top_contributor_share	0.913

Issue & PR responsiveness

70Good

How it's scored

37.7/42	Issue resolution — 90% of issues closed
18.5/30	PR acceptance — 16/26 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15	OpenSSF Scorecard: Code-Review — Found 9/28 approved changesets -- score normalized to 3

Inputs used

merged_prs	16
open_issues	4
closed_issues	35
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.897
closed_unmerged_prs	10
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

78Good

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
23.7/25	Owner reach — 2,001 followers of d3
24.7/25	Track record — 54 public repos, account ~14 yr old

Inputs used

followers	2,001
owner_type	Organization
is_verified	no
owner_login	d3
public_repos	54
account_age_days	5,275

Package maintenance

69Good

How it's scored

25/25	Published & resolvable — 1 package(s) on npm
4/35	Publish recency — latest publish 1,367 days ago
20/20	Version history — 38 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	d3-time
ecosystems	npm
any_deprecated	no
min_days_since_publish	1,367

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 19% of overall

Engineering practices

64Moderate

How it's scored

24/24	CI workflows — 2 workflow(s)
24/24	Tests present
16/16	Linter config — eslint.config.js
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — 0 out of 11 merged PRs checked by a CI test -- score normalized to 0

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
has_precommit_config	no

Documentation

55Moderate

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://d3js.org/d3-time
10/10	Repository description
0/10	Topics
0/10	Wiki

Inputs used

topics	—
has_wiki	no
homepage	https://d3js.org/d3-time
docs_site	https://d3js.org/d3-time
has_readme	yes
has_docs_dir	no
has_description	yes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

48Weak · 16% of overall

Security posture

35Weak

How it's scored

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

Inputs used

source	openssf_scorecard
checks_evaluated	16
scorecard_version	v5.5.0
checks_inconclusive	2
scorecard_aggregate	3.5

Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	2
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:d3-time@3.1.0 runtime dependency closure — what installing the published package pulls in — 2 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

39Weak · 4% of overall

Agent context & guidance

15Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
15.1/40	Legible commit history — 28 of 99 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.283
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

51Moderate

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
11/11	Lint / format config — eslint.config.js
0/11	Static type checking
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 100
8/8	Automated maintenance — 1 of the last 100 commits are automated dependency updates
0/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0

Inputs used

has_nix	no
has_tests	yes
lockfiles	yarn.lock
has_dockerfile	no
typed_language	no
bootstrap_files	—
has_devcontainer	no
has_linter_config	yes
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0.01

Code legibility for models

55Moderate

How it's scored

0/45	Type-checkable code — JavaScript without a type-check config
55/55	Manageable file sizes — 0/51 source files over 60KB

Inputs used

primary_language	JavaScript
largest_source_bytes	12,814
source_files_sampled	51
oversized_source_files	0

Key facts

238GitHub stars

8contributors

0commits, last 12 months

818days since last push

36releases

1bus factor

4open issues

npmpackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 54 ⇿

0Stars

54Forks

32Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

Major 3Minor 6Patch 23

Each point covers 10 days.

OpenSSF Scorecard 3.5 / 10

3.5aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-31 10:39 UTC

10	Binary-Artifacts	no binaries found in the repo
n/a	Branch-Protection	internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0	CI-Tests	0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
3	Code-Review	Found 9/28 approved changesets -- score normalized to 3
10	Contributors	project has 6 contributing companies or organizations
10	Dangerous-Workflow	no dangerous workflow patterns detected
10	Dependency-Update-Tool	update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
0	Maintained	0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/a	Packaging	packaging workflow not detected
0	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 0
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
0	Signed-Releases	Project has not signed or included provenance with any releases.
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
0	Vulnerabilities	24 existing vulnerabilities detected

Direct dependencies 1

Registry	Package	Version constraint	Manifest
npm	d3-array	`2 - 3`	package.json

All dependencies 177

Full resolved dependency set from the GitHub dependency graph: 1 direct and 176 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

Registry	Package	Version	Relation
npm	d3-array	`3.2.4`	direct
npm	@eslint-community/eslint-utils	`4.4.0`	indirect
npm	@eslint-community/regexpp	`4.10.1`	indirect
npm	@eslint/config-array	`0.15.1`	indirect
npm	@eslint/eslintrc	`3.1.0`	indirect
npm	@eslint/js	`9.4.0`	indirect
npm	@eslint/object-schema	`2.1.3`	indirect
npm	@humanwhocodes/module-importer	`1.0.1`	indirect
npm	@humanwhocodes/retry	`0.3.0`	indirect
npm	@jridgewell/gen-mapping	`0.3.5`	indirect
npm	@jridgewell/resolve-uri	`3.1.2`	indirect
npm	@jridgewell/set-array	`1.2.1`	indirect
npm	@jridgewell/source-map	`0.3.6`	indirect
npm	@jridgewell/sourcemap-codec	`1.4.15`	indirect
npm	@jridgewell/trace-mapping	`0.3.25`	indirect
npm	@nodelib/fs.scandir	`2.1.5`	indirect
npm	@nodelib/fs.stat	`2.0.5`	indirect
npm	@nodelib/fs.walk	`1.2.8`	indirect
npm	@rollup/plugin-terser	`0.4.4`	indirect
npm	@rollup/rollup-android-arm-eabi	`4.18.0`	indirect
npm	@rollup/rollup-android-arm64	`4.18.0`	indirect
npm	@rollup/rollup-darwin-arm64	`4.18.0`	indirect
npm	@rollup/rollup-darwin-x64	`4.18.0`	indirect
npm	@rollup/rollup-linux-arm-gnueabihf	`4.18.0`	indirect
npm	@rollup/rollup-linux-arm-musleabihf	`4.18.0`	indirect
npm	@rollup/rollup-linux-arm64-gnu	`4.18.0`	indirect
npm	@rollup/rollup-linux-arm64-musl	`4.18.0`	indirect
npm	@rollup/rollup-linux-powerpc64le-gnu	`4.18.0`	indirect
npm	@rollup/rollup-linux-riscv64-gnu	`4.18.0`	indirect
npm	@rollup/rollup-linux-s390x-gnu	`4.18.0`	indirect
npm	@rollup/rollup-linux-x64-gnu	`4.18.0`	indirect
npm	@rollup/rollup-linux-x64-musl	`4.18.0`	indirect
npm	@rollup/rollup-win32-arm64-msvc	`4.18.0`	indirect
npm	@rollup/rollup-win32-ia32-msvc	`4.18.0`	indirect
npm	@rollup/rollup-win32-x64-msvc	`4.18.0`	indirect
npm	@types/estree	`1.0.5`	indirect
npm	acorn	`8.11.3`	indirect
npm	acorn-jsx	`5.3.2`	indirect
npm	ajv	`6.12.6`	indirect
npm	ansi-colors	`4.1.1`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	anymatch	`3.1.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	binary-extensions	`2.3.0`	indirect
npm	brace-expansion	`1.1.11`	indirect
npm	brace-expansion	`2.0.1`	indirect
npm	braces	`3.0.3`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	buffer-from	`1.1.2`	indirect
npm	callsites	`3.1.0`	indirect
npm	camelcase	`6.3.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	chokidar	`3.5.3`	indirect
npm	cliui	`7.0.4`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	commander	`2.20.3`	indirect
npm	concat-map	`0.0.1`	indirect
npm	cross-spawn	`7.0.3`	indirect
npm	debug	`4.3.4`	indirect
npm	debug	`4.3.5`	indirect
npm	decamelize	`4.0.0`	indirect
npm	deep-is	`0.1.4`	indirect
npm	diff	`5.0.0`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	escalade	`3.1.2`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	eslint	`9.4.0`	indirect
npm	eslint-scope	`8.0.1`	indirect
npm	eslint-visitor-keys	`3.4.3`	indirect
npm	eslint-visitor-keys	`4.0.0`	indirect
npm	espree	`10.0.1`	indirect
npm	esquery	`1.5.0`	indirect
npm	esrecurse	`4.3.0`	indirect
npm	estraverse	`5.3.0`	indirect
npm	esutils	`2.0.3`	indirect
npm	fast-deep-equal	`3.1.3`	indirect
npm	fast-json-stable-stringify	`2.1.0`	indirect
npm	fast-levenshtein	`2.0.6`	indirect
npm	fastq	`1.17.1`	indirect
npm	file-entry-cache	`8.0.0`	indirect
npm	fill-range	`7.1.1`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat	`5.0.2`	indirect
npm	flat-cache	`4.0.1`	indirect
npm	flatted	`3.3.1`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	fsevents	`2.3.3`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	glob	`8.1.0`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	glob-parent	`6.0.2`	indirect
npm	globals	`14.0.0`	indirect
npm	globals	`15.3.0`	indirect
npm	has-flag	`4.0.0`	indirect
npm	he	`1.2.0`	indirect
npm	ignore	`5.3.1`	indirect
npm	import-fresh	`3.3.0`	indirect
npm	imurmurhash	`0.1.4`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	internmap	`2.0.3`	indirect
npm	is-binary-path	`2.1.0`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	indirect
npm	is-path-inside	`3.0.3`	indirect
npm	is-plain-obj	`2.1.0`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	js-yaml	`4.1.0`	indirect
npm	json-buffer	`3.0.1`	indirect
npm	json-schema-traverse	`0.4.1`	indirect
npm	json-stable-stringify-without-jsonify	`1.0.1`	indirect
npm	keyv	`4.5.4`	indirect
npm	levn	`0.4.1`	indirect
npm	locate-path	`6.0.0`	indirect
npm	lodash.merge	`4.6.2`	indirect
npm	log-symbols	`4.1.0`	indirect
npm	minimatch	`3.1.2`	indirect
npm	minimatch	`5.0.1`	indirect
npm	minimatch	`5.1.6`	indirect
npm	mocha	`10.4.0`	indirect
npm	ms	`2.1.2`	indirect
npm	ms	`2.1.3`	indirect
npm	natural-compare	`1.4.0`	indirect
npm	normalize-path	`3.0.0`	indirect
npm	once	`1.4.0`	indirect
npm	optionator	`0.9.4`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	parent-module	`1.0.1`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	picomatch	`2.3.1`	indirect
npm	prelude-ls	`1.2.1`	indirect
npm	punycode	`2.3.1`	indirect
npm	queue-microtask	`1.2.3`	indirect
npm	randombytes	`2.1.0`	indirect
npm	readdirp	`3.6.0`	indirect
npm	require-directory	`2.1.1`	indirect
npm	resolve-from	`4.0.0`	indirect
npm	reusify	`1.0.4`	indirect
npm	rollup	`4.18.0`	indirect
npm	run-parallel	`1.2.0`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	serialize-javascript	`6.0.0`	indirect
npm	serialize-javascript	`6.0.2`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	smob	`1.5.0`	indirect
npm	source-map	`0.6.1`	indirect
npm	source-map-support	`0.5.21`	indirect
npm	string-width	`4.2.3`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-color	`8.1.1`	indirect
npm	terser	`5.31.0`	indirect
npm	text-table	`0.2.0`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	type-check	`0.4.0`	indirect
npm	uri-js	`4.4.1`	indirect
npm	which	`2.0.2`	indirect
npm	word-wrap	`1.2.5`	indirect
npm	workerpool	`6.2.1`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs	`16.2.0`	indirect
npm	yargs-parser	`20.2.4`	indirect
npm	yargs-parser	`20.2.9`	indirect
npm	yargs-unparser	`2.0.0`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:d3-time@3.1.0 pulls in 2 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records