Replies: 2 comments 1 reply
-
Thank @bluthen! Yeah being able to have your own categories makes sense. Maybe something like this, in {
"audit": {
"licensePolicy": {
"categories": [
{ "name": "Custom", "licenses": ["MIT", "Apache-2.0"] }
],
"high": ["cat:Network Protective", "cat:Strongly Protective"],
"low": ["cat: Custom"],
}
}
} |
Beta Was this translation helpful? Give feedback.
1 reply
-
Done in #99 and released in v1.36.0! Updates to the docs are incoming, some notes are available in the PR description for now. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I think it can be useful to have an option to specify your own licenses.json. With your own licenses.json you can put whatever string of license you want in it. You can have your own categories.
Related to #90
Example, like CC-SA licenses are currently in Uncategorized (which should still bring up an issue for you to resolve), but I would probably put it in Protective. I can see where you might want your own categories of licenses for your particular project: non-commercial, not-gpl-compatible, etc.
Beta Was this translation helpful? Give feedback.
All reactions