HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
BBC-News
wraith
OPEN SOURCE2013–2019
BBC-News / wraith

wraith

Discover this repository through its Hacker News conversations.

15Distinct people
15Mentions
0Explicit recommenders
0GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year15 dated mentions

Observed mentions: 2013-07-31 17:36:31 UTC to 2019-03-03 22:14:09 UTC.

012342013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC312
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC202
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC404
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC303
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
broken link vulnerability by Shamim ( hackerone @shamim_12__)
Read the full README on GitHub

What Hacker News says

15 sources
Screenshots are useful, but diffs of screenshots are even more useful. You could maybe immitate the workflow used by wraith? https://github.com/bbc-news/wraith For example to setup screenshot diffs between an existing production site and local dev, use: # (required) The domains to take screenshots of. domains: current: "https://prod.yoursite.com" new: "http://localhost:8000" paths: home: /pageyouareworkingon.html Not sure how to connect to localhost 8000 from the web though...
In Show HN: Screen.rip – API for capturing web screenshots
Wraith is super useful for web development on existing complex sites and I rarely hear of it or existing tools. Setup a staging site along with your production site, list the important URLs and when you run Wraith it'll compare screenshots of changes between the URLs on staging and production. This lets you update existing pages and verify you've not broken other pages with only a small amount of setup. See https://github.com/BBC-News/wraith
In Ask HN: What are some of useful but little-known tools you use for development?
We've been using a similar tool (https://github.com/BBC-News/wraith) for a little while now and it's transformed our way of working - 50 page layouts x 5 responsive breakpoints verified with a high degree of confidence in minutes on every build. Well worth the effort to take the time to set up such a tool, particularly if you have a large UI test matrix - we couldn't possibly verify all the different page layouts and sizes before we introduced wraith
In Pediff – tools for visually comparing web pages
What types of tests—or testing software—could be run on a WordPress site? For example, after we update a plugin on a WordPress site we manually check that the site hasn't changed in appearance. What software – or methodology – would you recommend for automating this game of spot-the-difference? The nearest I've found (but not tried) are: Screenster: http://www.creamtec.com/products/screenster/index.html Wraith: https://github.com/BBC-News/wraith
In Strategies to quickly become productive in an unfamiliar codebase

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.