License violation
@bastien-roucaries is already working on this.
Since Sep 5, 2017.
Assessment
This issue has not been assessed yet.
Description
you said that your package derive from:
ttps://code.google.com/p/crypto-js/
This is the license that is more restrictive than our. You should therefore use the following license and acknowledge original license:
Export to GitHub
crypto-js - License.wiki
(c) 2009-2013 by Jeff Mott. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation or other materials provided with the distribution.
Neither the name CryptoJS nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS," AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- Dominant language
- JavaScript
- Stars
- 62
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from browserify/browserify-aes
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
browserify/browserify-aes#66 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
browserify/browserify-aes#62 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
browserify/browserify-aes#61 · 1 comment ·
-
RangeError in authCipher.jsMay be free again @calvinmetcalf claimed this 2864 days ago, and no pull request is open. Open
browserify/browserify-aes#58 · 4 comments · 1 assignee ·
-
Incompatible with buffer-xor 2Possibly taken @kt3k claimed this 1683 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
browserify/browserify-aes#52 · 2 comments ·
All issues in browserify/browserify-aes
Similar issues
-
chore v2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/servers#5115 ·
Maintainers usually reply within 1 day
-
beginner bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
philaconvalley/website#168 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
druxt/umami.demo.druxtjs.org#527 ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NuSkooler/enigma-bbs#907 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100