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.
7 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 22d6b0fd9b15
head 70d2e8a2b9ed
head a4a9a76e4cd9
head 77d59fc4a3ee
head 5ffa9644b724
head 2e670951fe25
head 0b5043ab4123
Content fingerprint 5f4850169fb168de