Question 1

Is Homespun or Postgres · modelcontextprotocol better?

Accepted Answer

Homespun scores 68.0 and Postgres · modelcontextprotocol scores 18.0 on the tashan score, which measures upkeep and freshness gated by real adoption. Neither number is a security audit and neither can be bought. The gap is wide enough to be decisive.

Question 2

Are Homespun and Postgres · modelcontextprotocol safe to install?

Accepted Answer

Homespun: no known advisories, no build provenance. Postgres · modelcontextprotocol: no known advisories, no build provenance. Every capability tashan measures is checked against the OSV advisory database at the version you would install today, for install-time scripts and for build provenance. The audit reads public evidence and never executes anything.

Question 3

How were these two compared?

Accepted Answer

Both were measured on the same day by the same scorer, from public signal only — npm download volume and publish cadence, repository activity, maintainer count and registry status. Nobody can pay to change a score, a rank or a listing.

	Homespun	Postgres · modelcontextprotocol	what it means
tashan score	68	18	upkeep + freshness, gated by adoption
Adoption evidence	1k/wk	127k/wk	the raw public signal the score came from
Last release	active	abandoned	npm publish or repo push
Upkeep	70	18	cadence, maintainers, status
Expertise grade	thin	not graded	an LLM read of its own documentation against a fixed rubric
Security audit	no known advisories, no build provenance	no known advisories, no build provenance	existence of findings is always free; the detail a licence buys is on each dossier
Licence	—	MIT
Maintainers	one primary	more than one	bus-factor risk

Homespun vs Postgres · modelcontextprotocol

Install either