Loading the registry…
for venancio-matheus/awesome-chatgpt-prompts
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.
3 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.
Every row here carries the same head commit, so nothing in this evidence puts one before another. The repository their history continues in sits outside this group, and it may not be in the registry at all.
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.
Shared head commit 9a5acf16fb1f
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 9a5acf16fb1f
head 9a5acf16fb1f
Content fingerprint 8d33a43d4c7586bc
head 9a5acf16fb1f