Licence and preferred attribution for Technology Report data

Uncategorized
1

Hi all,

I run inetgeek.com, a small comparison site for hosting and infrastructure
providers. I’ve started using the Technology Report API to show per-category
adoption bars — for example the three PaaS providers I track, sized by origins
detected in the latest crawl, linking back to the relevant tech report page.

Two things I couldn’t resolve from the docs, and I’d rather ask than assume:

  1. Is there a licence for the Technology Report / HTTP Archive dataset itself?
    I checked the FAQ, the About page, har.fyi and the GitHub org. I can see
    httparchive.org and data-pipeline are Apache-2.0 and the Wappalyzer fork is
    GPL-3.0, but those cover code rather than the output numbers. Is the data
    CC0, CC-BY, or something else?

  2. Is there a preferred attribution string? Right now each chart reads
    “Source: HTTP Archive” and links to
    HTTP Archive: Tech Report . Happy to change the wording
    or the link target if you’d rather it pointed somewhere specific.

For what it’s worth, usage is tiny: one build-time request per month, and the
numbers are cached in the repo rather than fetched per page view.

One small note in case it’s useful to the team: a few technologies that exist in
the catalogue are easy to mistake for a different vendor of the same name —
“Doppler” is fromdoppler.com (email marketing) rather than doppler.com (the
secrets manager), and “Neon CRM” is Neon One rather than neon.com (Postgres).
Not a bug, just a trap for anyone matching vendor names automatically.

Thanks for publishing this openly — it’s the only free source I found that
counts the same kind of thing as the commercial crawlers.

2

Yeah we should really define this better!

Here’s what we last said about this: What are the rights/licensing for data in HTTP Archive?

TLDR: We’re happy (and encourage!) people to use the data and attribution is appreciated, but not required.

Of course some of the data is what’s collected from crawls of the public web so reusing assets from those websites may carry their own licencing terms and conditions. But for the aggregate stats that the HTTP Archive produces we’re happy for it to be re-used.