Skip to content
This repository was archived by the owner on Aug 11, 2022. It is now read-only.

Commit 8f71038

Browse files
rvaggzkat
authored andcommitted
license: update LICENSE to match current master
Credit: @rvagg Reviewed-By: @othiym23 PR-URL: #13892
1 parent 1b44849 commit 8f71038

File tree

1 file changed

+0
-46
lines changed

1 file changed

+0
-46
lines changed

LICENSE

Lines changed: 0 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -233,49 +233,3 @@ ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
233233

234234

235235
--------
236-
237-
238-
The following additional terms shall apply to use of the npm software, the npm
239-
website, the npm repository and any other services or products offered by npm,
240-
Inc.:
241-
242-
"Node.js" trademark Joyent, Inc. npm is not officially part of the Node.js
243-
project, and is neither owned by nor affiliated with Joyent, Inc.
244-
245-
"npm" and "The npm Registry" are owned by npm, Inc. All rights reserved.
246-
247-
Modules published on the npm registry are not officially endorsed by npm, Inc.
248-
or the Node.js project.
249-
250-
Data published to the npm registry is not part of npm itself, and is the sole
251-
property of the publisher. While every effort is made to ensure accountability,
252-
there is absolutely no guarantee, warrantee, or assertion expressed or implied
253-
as to the quality, fitness for a specific purpose, or lack of malice in any
254-
given npm package. Packages downloaded through the npm registry are
255-
independently licensed and are not covered by this license.
256-
257-
Additional policies relating to, and restrictions on use of, npm products and
258-
services are available on the npm website. All such policies and restrictions,
259-
as updated from time to time, are hereby incorporated into this license
260-
agreement. By using npm, you acknowledge your agreement to all such policies
261-
and restrictions.
262-
263-
If you have a complaint about a package in the public npm registry, and cannot
264-
resolve it with the package owner, please email [email protected] and explain
265-
the situation. See the [npm Dispute Resolution
266-
policy](https://github.com/npm/policies/blob/master/disputes.md) for more
267-
details.
268-
269-
Any data published to The npm Registry (including user account information) may
270-
be removed or modified at the sole discretion of the npm server administrators.
271-
272-
"npm Logo" contributed by Mathias Pettersson and Brian Hammond,
273-
use is subject to https://www.npmjs.com/policies/trademark
274-
275-
"Gubblebum Blocky" font
276-
Copyright (c) by Tjarda Koster, https://jelloween.deviantart.com
277-
included for use in the npm website and documentation,
278-
used with permission.
279-
280-
This program uses several Node modules contained in the node_modules/
281-
subdirectory, according to the terms of their respective licenses.

0 commit comments

Comments
 (0)