npm-www

Discover this repository through its Hacker News conversations.

Explore on GitHub Read Hacker News discussions

3Distinct people

3Mentions

0Explicit recommenders

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 has been verified yet.

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

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 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 month3 dated mentions

Observed mentions: 2014-02-06 07:38:52 UTC to 2014-09-18 16:51:29 UTC.

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.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Feb 2014	2014-02-01 00:00:00 UTC	2014-03-01 00:00:00 UTC	1	1
Mar 2014	2014-03-01 00:00:00 UTC	2014-04-01 00:00:00 UTC	1	1
Apr 2014	2014-04-01 00:00:00 UTC	2014-05-01 00:00:00 UTC	0	0
May 2014	2014-05-01 00:00:00 UTC	2014-06-01 00:00:00 UTC	0	0
Jun 2014	2014-06-01 00:00:00 UTC	2014-07-01 00:00:00 UTC	0	0
Jul 2014	2014-07-01 00:00:00 UTC	2014-08-01 00:00:00 UTC	0	0
Aug 2014	2014-08-01 00:00:00 UTC	2014-09-01 00:00:00 UTC	0	0
Sep 2014	2014-09-01 00:00:00 UTC	2014-10-01 00:00:00 UTC	1	1

What Hacker News says

3 sources

phadej·Sep 18, 2014

Wow, someone had time and motivation to write all of that boilerplate there. Yet e.g. the license parsing is very naive: compare https://github.com/npm/npm-www/blob/99020b5b3e21607dab24cd69... and https://github.com/rickbergfalk/npm-postgres-mashup/blob/56d...

In NPM registry in numbers

chjj·Mar 21, 2014

If it's referring to what I think it is, part of this is my fault and I feel I should give a post-mortem as well. There was a problem with marked (the markdown parser npmjs.org uses for READMEs) which allowed users to provide `javascript:` pseudo-protocol links even when the `sanitize` option was enabled. It was fixed[1] with marked v0.3.1 on jan. 31st. It looks like npm-www started using marked v0.3.1 on feb. 17th[2]. [1] https://github.com/chjj/marked/commit/904c71b7713979b01d5bc5... [2] https://github.com/npm/npm-www/commit/a1ed923870609b578fcde4... edit: On closer inspection it looks like it may have been a problem with the html sanitizer[3] it used as opposed to the marked `sanitize` option (which is not used at all). I guess my conscience is clear here at least. [3] https://github.com/npm/npm-www/blob/master/models/package.js...

In Npm security post-mortem

seldo·Feb 6, 2014

No added value, just haven't got around to implementing anything cleverer, yet. There is an open issue: https://github.com/npm/npm-www/issues/569 Feel free to chime in if you have a suggestion or even submit a patch; npm Inc only has 4 full-time engineers right now (we're hiring!) so it will be a while before we get to this otherwise :-)

In New npm Registry Architecture