Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 03:56 UTC

tristen / tablesort

:arrow_up_down: A small tablesorter in plain JavaScript

JavaScriptMIT★ 1,144 stars⑂ 180 forkssince Mar 2012View on GitHub ↗

tristen/tablesort holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (74/100) and lowest on AI Readiness (43/100). It was last updated 157 days ago. A single contributor accounts for most of its recent work.

overall / 100

Good

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 61 is calibrated to 67 on the published index scale (record calibration 2026-08-02).

Ownership

Tristen BrownPersonal account

335 followers64 public repossince Mar 2009@mapbox

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish
npm	tablesort	5.7.1	2,129,969	44	157 days ago

Metrics by category

Vitality

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

45Weak · 21% of overall

Development activity

26At Risk

How it's scored

9.9/36	Push recency — last push 157 days ago
3.5/36	Commit cadence — 5/52 weeks with commits
12.7/18	Commit volume — 25 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	25
human_commit_share	0.85
days_since_last_push	157
active_weeks_last_year	5

Release discipline

74Good

How it's scored

27/27	Ships releases — 24 releases published
27/36	Release recency — latest release 157 days ago
12.6/27	Release cadence — a release every ~360.6 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	24
latest_release_tag	5.7.1
releases_from_tags	no
days_since_latest_release	157
mean_days_between_releases	360.6

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

Community & Adoption

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

73Good · 17% of overall

Popularity & adoption

77Good

How it's scored

49.6/60	Stars — 1,144 stars
18.8/25	Forks — 180 forks
8.2/15	Watchers — 31 watchers

Inputs used

forks	180
stars	1,144
watchers	31
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 (MIT)
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	2
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	shields.io, travis-ci.com
has_pull_request_template	no

Ecosystem adoption (downloads)

100Exceptional

How it's scored

80/80	Monthly downloads — 2,129,969 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	tablesort
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	2,129,969
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?

66Good · 23% of overall

Maintainer resilience (bus factor)

42Weak

How it's scored

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

Inputs used

bus_factor	1
contributors_sampled	33
top_contributor_share	0.565

Issue & PR responsiveness

68Good

How it's scored

30.6/42	Issue resolution — 73% of issues closed
21.4/30	PR acceptance — 77/108 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
7.5/15	OpenSSF Scorecard: Code-Review — Found 7/14 approved changesets -- score normalized to 5

Inputs used

merged_prs	77
open_issues	39
closed_issues	105
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	0.729
closed_unmerged_prs	31
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

66Good

How it's scored

10/30	Ownership backing — personal (user) account
0/20	Verified domain — not applicable to user accounts
18.2/25	Owner reach — 335 followers of tristen
25/25	Track record — 64 public repos, account ~17 yr old

Inputs used

followers	335
owner_type	User
is_verified	—
owner_login	tristen
public_repos	64
account_age_days	6,405

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional

How it's scored

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

Inputs used

packages	tablesort
ecosystems	npm
any_deprecated	no
min_days_since_publish	157

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall

Engineering practices

74Good

How it's scored

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

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	yes
has_linter_config	yes
has_precommit_config	no

Documentation

75Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://tristen.ca/tablesort/demo/
10/10	Repository description
10/10	Topics — 2 topics
10/10	Wiki

Inputs used

topics	tablesort, javascript
has_wiki	yes
homepage	https://tristen.ca/tablesort/demo/
docs_site	https://tristen.ca/tablesort/demo/
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?

53Moderate · 16% of overall

Security posture

41Weak

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
2.2/7.5	Branch-Protection — branch protection is not maximal on development and all release branches
0.5/2.5	CI-Tests — 3 out of 12 merged PRs checked by a CI test -- score normalized to 2
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5	Code-Review — Found 7/14 approved changesets -- score normalized to 5
2.5/2.5	Contributors — project has 11 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
1.5/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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 — no data
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5	Vulnerabilities — 19 existing vulnerabilities detected

Inputs used

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

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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
0/25	Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	19
affected_packages	7
assessed_packages	181
unassessed_packages	0
affected_by_severity	high 7
direct_affected_packages	0

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 181 resolved dependencies against OSV. 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.

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.

43Weak · 4% of overall

Agent context & guidance

24At Risk

How it's scored

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

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.459
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

54Moderate

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
11/11	Lint / format config — .eslintrc
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 — 15 of the last 100 commits are automated dependency updates
3/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
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.15

Code legibility for models

52Moderate

How it's scored

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

Inputs used

primary_language	JavaScript
largest_source_bytes	149,368
source_files_sampled	18
oversized_source_files	1

Key facts

1,144GitHub stars

33contributors

25commits, last 12 months

157days since last push

24releases

1bus factor

39open issues

npmpackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
deps.dev does not index npm:tablesort@5.7.1; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 180 ⇿

0Stars

180Forks

23Releases

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 10Patch 10

Each point covers 13 days.

OpenSSF Scorecard 4.1 / 10

4.1aggregate

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-09-20 03:56 UTC

10	Binary-Artifacts	no binaries found in the repo
3	Branch-Protection	branch protection is not maximal on development and all release branches
2	CI-Tests	3 out of 12 merged PRs checked by a CI test -- score normalized to 2
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
5	Code-Review	Found 7/14 approved changesets -- score normalized to 5
10	Contributors	project has 11 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
3	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 3
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
0	Vulnerabilities	19 existing vulnerabilities detected

All dependencies 181

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

Registry	Package	Version	Relation
npm	@asamuzakjp/css-color	`3.2.0`	indirect
npm	@csstools/color-helpers	`5.0.2`	indirect
npm	@csstools/css-calc	`2.1.4`	indirect
npm	@csstools/css-color-parser	`3.0.10`	indirect
npm	@csstools/css-parser-algorithms	`3.0.5`	indirect
npm	@csstools/css-tokenizer	`3.0.4`	indirect
npm	abbrev	`1.1.1`	indirect
npm	agent-base	`7.1.3`	indirect
npm	ansi-regex	`2.1.1`	indirect
npm	ansi-styles	`2.2.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	argparse	`1.0.10`	indirect
npm	array-each	`1.0.1`	indirect
npm	array-slice	`1.1.0`	indirect
npm	async	`3.2.6`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	brace-expansion	`1.1.11`	indirect
npm	braces	`3.0.3`	indirect
npm	buffer-shims	`1.0.0`	indirect
npm	chalk	`1.1.3`	indirect
npm	chalk	`4.1.2`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	colors	`1.1.2`	indirect
npm	concat-map	`0.0.1`	indirect
npm	core-util-is	`1.0.3`	indirect
npm	cssstyle	`4.3.1`	indirect
npm	data-urls	`5.0.0`	indirect
npm	dateformat	`4.6.3`	indirect
npm	debug	`4.4.1`	indirect
npm	decimal.js	`10.5.0`	indirect
npm	detect-file	`1.0.0`	indirect
npm	duplexer	`0.1.2`	indirect
npm	entities	`6.0.0`	indirect
npm	escape-string-regexp	`1.0.5`	indirect
npm	esprima	`4.0.1`	indirect
npm	eventemitter2	`0.4.14`	indirect
npm	exit	`0.1.2`	indirect
npm	expand-tilde	`2.0.2`	indirect
npm	extend	`3.0.2`	indirect
npm	figures	`1.7.0`	indirect
npm	figures	`3.2.0`	indirect
npm	fill-range	`7.1.1`	indirect
npm	findup-sync	`4.0.0`	indirect
npm	findup-sync	`5.0.0`	indirect
npm	fined	`1.2.0`	indirect
npm	flagged-respawn	`1.0.1`	indirect
npm	for-in	`1.0.2`	indirect
npm	for-own	`1.0.0`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	function-bind	`1.1.2`	indirect
npm	getobject	`1.0.2`	indirect
npm	glob	`7.1.7`	indirect
npm	global-modules	`1.0.0`	indirect
npm	global-prefix	`1.0.2`	indirect
npm	grunt	`1.6.1`	indirect
npm	grunt-cli	`1.4.3`	indirect
npm	grunt-cli	`1.5.0`	indirect
npm	grunt-contrib-uglify	`5.2.2`	indirect
npm	grunt-known-options	`2.0.0`	indirect
npm	grunt-legacy-log	`3.0.0`	indirect
npm	grunt-legacy-log-utils	`2.1.0`	indirect
npm	grunt-legacy-util	`2.0.1`	indirect
npm	gzip-size	`5.1.1`	indirect
npm	has-ansi	`2.0.0`	indirect
npm	has-flag	`4.0.0`	indirect
npm	hasown	`2.0.2`	indirect
npm	homedir-polyfill	`1.0.3`	indirect
npm	hooker	`0.2.3`	indirect
npm	html-encoding-sniffer	`4.0.0`	indirect
npm	http-proxy-agent	`7.0.2`	indirect
npm	https-proxy-agent	`7.0.6`	indirect
npm	iconv-lite	`0.6.3`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	ini	`1.3.8`	indirect
npm	interpret	`1.1.0`	indirect
npm	is-absolute	`1.0.0`	indirect
npm	is-core-module	`2.16.1`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-finite	`1.1.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	indirect
npm	is-plain-object	`2.0.4`	indirect
npm	is-potential-custom-element-name	`1.0.1`	indirect
npm	is-relative	`1.0.0`	indirect
npm	is-unc-path	`1.0.0`	indirect
npm	is-windows	`1.0.2`	indirect
npm	isarray	`1.0.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	isobject	`3.0.1`	indirect
npm	js-yaml	`3.14.2`	indirect
npm	jsdom	`26.1.0`	indirect
npm	kind-of	`6.0.3`	indirect
npm	liftup	`3.0.1`	indirect
npm	lodash	`4.17.23`	indirect
npm	lru-cache	`10.4.3`	indirect
npm	make-iterator	`1.0.1`	indirect
npm	map-cache	`0.2.2`	indirect
npm	maxmin	`3.0.0`	indirect
npm	micromatch	`4.0.8`	indirect
npm	minimatch	`3.0.8`	indirect
npm	ms	`2.1.3`	indirect
npm	nopt	`3.0.6`	indirect
npm	nopt	`4.0.3`	indirect
npm	nopt	`5.0.0`	indirect
npm	nwsapi	`2.2.20`	indirect
npm	object-assign	`4.1.1`	indirect
npm	object.defaults	`1.1.0`	indirect
npm	object.map	`1.0.1`	indirect
npm	object.pick	`1.3.0`	indirect
npm	once	`1.4.0`	indirect
npm	os-homedir	`1.0.2`	indirect
npm	os-tmpdir	`1.0.2`	indirect
npm	osenv	`0.1.5`	indirect
npm	parse-filepath	`1.0.2`	indirect
npm	parse-ms	`1.0.1`	indirect
npm	parse-passwd	`1.0.0`	indirect
npm	parse5	`7.3.0`	indirect
npm	path-is-absolute	`1.0.1`	indirect
npm	path-parse	`1.0.7`	indirect
npm	path-root	`0.1.1`	indirect
npm	path-root-regex	`0.1.2`	indirect
npm	picomatch	`2.3.1`	indirect
npm	pify	`4.0.1`	indirect
npm	plur	`1.0.0`	indirect
npm	pretty-bytes	`5.6.0`	indirect
npm	pretty-ms	`2.1.0`	indirect
npm	process-nextick-args	`1.0.7`	indirect
npm	process-nextick-args	`2.0.1`	indirect
npm	punycode	`2.3.1`	indirect
npm	re-emitter	`1.1.3`	indirect
npm	readable-stream	`2.2.9`	indirect
npm	readable-stream	`2.3.8`	indirect
npm	rechoir	`0.7.1`	indirect
npm	repeat-string	`1.6.1`	indirect
npm	resolve	`1.22.10`	indirect
npm	resolve-dir	`1.0.1`	indirect
npm	rrweb-cssom	`0.8.0`	indirect
npm	safe-buffer	`5.1.2`	indirect
npm	safer-buffer	`2.1.2`	indirect
npm	saxes	`6.0.0`	indirect
npm	split	`1.0.0`	indirect
npm	sprintf-js	`1.0.3`	indirect
npm	sprintf-js	`1.1.3`	indirect
npm	string_decoder	`1.0.3`	indirect
npm	string_decoder	`1.1.1`	indirect
npm	strip-ansi	`3.0.1`	indirect
npm	supports-color	`2.0.0`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-preserve-symlinks-flag	`1.0.0`	indirect
npm	symbol-tree	`3.2.4`	indirect
npm	tap-out	`2.1.0`	indirect
npm	tap-spec	`5.0.0`	indirect
npm	through	`2.3.8`	indirect
npm	through2	`2.0.5`	indirect
npm	tldts	`6.1.86`	indirect
npm	tldts-core	`6.1.86`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	tough-cookie	`5.1.2`	indirect
npm	tr46	`5.1.1`	indirect
npm	trim	`0.0.1`	indirect
npm	uglify-js	`3.19.3`	indirect
npm	unc-path-regex	`0.1.2`	indirect
npm	underscore.string	`3.3.6`	indirect
npm	uri-path	`1.0.0`	indirect
npm	util-deprecate	`1.0.2`	indirect
npm	v8flags	`3.2.0`	indirect
npm	v8flags	`4.0.1`	indirect
npm	w3c-xmlserializer	`5.0.0`	indirect
npm	webidl-conversions	`7.0.0`	indirect
npm	whatwg-encoding	`3.1.1`	indirect
npm	whatwg-mimetype	`4.0.0`	indirect
npm	whatwg-url	`14.2.0`	indirect
npm	which	`1.3.1`	indirect
npm	which	`2.0.2`	indirect
npm	wrappy	`1.0.2`	indirect
npm	ws	`8.18.2`	indirect
npm	xml-name-validator	`5.0.0`	indirect
npm	xmlchars	`2.2.0`	indirect
npm	xtend	`4.0.2`	indirect

Dependency advisories 7

This repository publishes no package the index resolves, so its own dependency graph was assessed — 181 packages, which also include development and test pins that never ship: 7 carry known advisories, of which 0 are direct.

Package	Version	Relation	Severity	Advisories	Fixed in
brace-expansion	`1.1.11`	indirect	high	5	`5.0.9`
js-yaml	`3.14.2`	indirect	high	4	`4.3.2`
lodash	`4.17.23`	indirect	high	2	`4.18.0`
minimatch	`3.0.8`	indirect	high	3	`10.2.3`
picomatch	`2.3.1`	indirect	high	2	`4.0.4`
trim	`0.0.1`	indirect	high	1	`0.0.3`
ws	`8.18.2`	indirect	high	2	`8.21.0`

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