Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Missing licensing information #2

dpaleino opened this Issue · 7 comments

4 participants



I'm packaging node-crc for Debian, and it's missing any licensing information. The only information is in the code, and refers to the various original pieces of software you took parts from.

Also, some parts of the code are taken from RFCs. Unfortunately, RFC documents aren't free for use, but are copyrighted by the IETF. Please have a look at RFC2223, section #11.

Thank you,


@dpaleino I didn't know about RFC copyright. I'm not sure what would be the proper license for this package in this case. Any suggestions?


@alexgorbatchev thanks for replying.

The best course of action would be implementing functions that generate, from scratch, the tables. An example of such code is at -- but that's in Ada, not Javascript. I also found a Python example, which might be more suitable to re-implement with Javascript: .


I'd love to see the licence in the git hub repo too ;-) There is existing python generator for those tables, can you use it to generate those? Its MIT licence, but the output is "yours".


Hmm I tried to generate and the output is totally different ;-) I am not a CRC expert, what is wrong with it?

 python --model crc-8 --algorithm table-driven --generate c -o crc.c

Edit: I have tested my table with the following algorithm and it works:


Hi Alex,

I saw there has been an update a couple of day´s ago, is it possible to release this module under a proper license now (maybe MIT)?




@piscis I don't believe the license issue has been resolved

@wavded wavded referenced this issue from a commit in wavded/connect
@mdp mdp Replace 'node-crc' with 'buffer-crc32', fixes licensing
The 'crc' package is using code that is not freely licensed(MIT/BSD)

Express also moved to 'buffer-crc32' recently because of this issue.

Fixes senchalabs/connect#712

License is now MIT based on full rewrite from another MIT Ruby module

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.