Loading the registry…
for remote-mcp-server-authless
Identical content is a measurement, not a finding. Many packages are published under licences that permit redistribution, and a copy being identical says nothing about why it exists or whether it should.
11 registry rows carry byte-for-byte identical content, including this one.
Rows are grouped by their content only. A row that shares this one’s name but differs by a single byte is not in this group and keeps its own listing entry — that is what makes a republished version with something added stay separately visible.
The commit histories differ, but no evidence available identifies which of these came first.
We do not break this tie by star count, repository age, or the order we happened to index these rows. None of those measure where content came from, and each of them would produce a confident answer that can be wrong — so no row here is marked as the original.
Git does not verify the identity recorded in a commit, and whoever published a repository is not necessarily whoever authored the commits in it.
Each row keeps its own listing entry and its own scanner results. This list intentionally shows no verdicts — open a row to see what its scanners found.
head acc0bd7ca3d3
head b31c65c601e8
head 482f1923f006
head 73752439788d
head 1a9a61ea6169
head 950532781fc7
head db1a93a025d2
head 9b21e5770c48
head 2b6cdffe293d
head 197c00cadd8d
head 34155b45d05f
Content fingerprint cfca8c03b2b0e6ed