2018-10-25 18:29:56 +00:00
---
id: 587d7fb4367417b2b2512bfe
title: Add a License to Your package.json
challengeType: 2
2019-08-05 16:17:33 +00:00
forumTopicId: 301523
2021-01-13 02:31:00 +00:00
dashedName: add-a-license-to-your-package-json
2018-10-25 18:29:56 +00:00
---
2020-11-27 18:02:05 +00:00
# --description--
The `license` field is where you inform users of what they are allowed to do with your project.
2019-03-03 18:30:44 +00:00
Some common licenses for open source projects include MIT and BSD. License information is not required, and copyright laws in most countries will give you ownership of what you create by default. However, it’ s always a good practice to explicitly state what users can and can’ t do. Here's an example of the license field:
2019-05-14 12:00:06 +00:00
```json
"license": "MIT",
```
2020-11-27 18:02:05 +00:00
# --instructions--
2018-10-25 18:29:56 +00:00
2020-11-27 18:02:05 +00:00
Fill the `license` field in the package.json file of your project as you find suitable.
2018-10-25 18:29:56 +00:00
2020-11-27 18:02:05 +00:00
# --hints--
2018-10-25 18:29:56 +00:00
2020-11-27 18:02:05 +00:00
package.json should have a valid "license" key
2018-10-25 18:29:56 +00:00
2020-11-27 18:02:05 +00:00
```js
(getUserInput) =>
$.get(getUserInput('url') + '/_api/package.json').then(
(data) => {
var packJson = JSON.parse(data);
assert(packJson.license, '"license" is missing');
},
(xhr) => {
throw new Error(xhr.responseText);
}
);
2018-10-25 18:29:56 +00:00
```
2020-11-27 18:02:05 +00:00
# --solutions--
2018-10-25 18:29:56 +00:00
```js
2019-10-24 04:38:13 +00:00
/**
Backend challenges don't need solutions,
because they would need to be tested against a full working project.
Please check our contributing guidelines to learn more.
*/
2018-10-25 18:29:56 +00:00
```