\n \n\n\n\n\n\n## About The Project\n\n![Command-line usage][product-screenshot]\n\nThe SPDX syntax for expressing license terms comes from the [Software Package Data eXchange (SPDX)](https://spdx.org/), a standard from the [Linux Foundation](https://www.linuxfoundation.org/) for shareable data about software package license terms. SPDX aims to make sharing and auditing license data easy, especially for users of open-source software.\n\nThere are plenty of NPM packages available for dealing with SPDX license expressions, each with their specific scope and objectives – and, conversely, they all make some assumptions that may or may not suit your purposes. Many of these packages also lack support (types) for TypeScript.\n\nThe particular challenge that soon gave birth to `license-expressions` was that libraries such as `spdx-expression-parse` produce a parse tree but require each license identifier to be a known SPDX license.\n\nThe objective of `license-expressions` is to support building automation tools that deal with license information in bulk or otherwise without ability to correct sloppy or outright invalid license expressions one by one, for example, when processing hundreds or thousands of direct and transitive dependencies of as part of a software audit.\n\n
\n\n\n\n## Getting Started\n\nThis is an example of how you may give instructions on setting up your project locally.\nTo get a local copy up and running follow these simple example steps.\n\n### Prerequisites\n\nThis is an example of how to list things you need to use the software and how to install them.\n* npm\n ```sh\n npm install npm@latest -g\n ```\n\n### Installation for command line use\n\n**With a global install from the NPM registry:**\n\n1. Install the NPM package globally\n ```sh\n $ npm install -g license-expressions\n ```\n\n**By cloning the Git repository and installing locally:**\n\n1. Clone the repo\n ```sh\n $ git clone https://github.com/lkoskela/license-expressions.git\n ```\n2. Install NPM packages\n ```sh\n $ npm install\n ```\n3. Link the CLI entrypoint to your PATH\n ```sh\n $ npm link\n ```\n\n
\n\n### Installation for programmatic use\n\n1. Install the `license-expressions` package as a dependency\n ```sh\n $ npm install --save license-expressions\n ```\n2. Import the parse function in your code...\n ```js\n const parse = require('license-expressions')\n ```\n3. ...or import the whole set:\n ```js\n import { parse, normalize, validate } from 'license-expressions'\n ```\n\n
\n\n\n\n\n## Roadmap\n\nThere is currently not much of a roadmap.\n\nThe rough idea is to first reach a sufficient level of correctness and robustness within the realm of valid SPDX expressions with valid license identifiers. This is mostly in place already.\n\nThe subsequent evolutionary step is to add the ability to correct slightly mistyped or liberal references to valid licenses, i.e. parse an input such as parsing `\"Apache 2\"` into `{ license: Apache-2.0 }`, or parsing `\"Apache2 or MIT\"` into `{ conjunction: 'or', left: { license: 'Apache-2.0' }, right: { license: 'MIT } }`. The basics for such corrections are in place with the help of a secondary, looser parser grammar, the `spdx-correct` third-party library, and additional heuristics/corrections implemented in this library.\n\nRight now we're at a phase where all the major functionality is in place and need for change comes primarily from stumbling onto a live example of a license expression that the library doesn't manage to coerce into a valid format while it seems like a feasible thing to do.\n\n\n\nSee the [open issues](https://github.com/lkoskela/license-expressions/issues) for a full and up to date list of proposed features (and known issues).\n\n
\n\n\n\n## Contributing\n\nContributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.\n\nIf you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag \"enhancement\". Don't forget to give the project a star! Thanks again!\n\n1. Fork the Project\n2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)\n3. Commit your Changes (`git commit -m 'Add some AmazingFeature'`)\n4. Push to the Branch (`git push origin feature/AmazingFeature`)\n5. Once you feel good about the contribution, its tests all pass (`npm test`) and test coverage looks good, go ahead and open a Pull Request\n\n
\n\n\n\n\n## License\n\nDistributed under the MIT License. See [LICENSE][license-url] for more information.\n\nThe Linux Foundation and its contributors license the SPDX standard under the terms of [the Creative Commons Attribution License 3.0 Unported (SPDX: \"CC-BY-3.0\")](http://spdx.org/licenses/CC-BY-3.0). \"SPDX\" is a United States federally registered trademark of the [Linux Foundation](https://www.linuxfoundation.org/). The authors of this package license their work under the terms of the [MIT License](https://spdx.org/licenses/MIT.html).\n\n
\n\n\n\n\n## Acknowledgments\n\n* [Othneil Drew](https://github.com/othneildrew) for the [Best-README-Template](https://github.com/othneildrew/Best-README-Template)\n\n