license-checker VS Standard

I thought that was a fairly weird question. A couple of our APIs run on Ubuntu, which contains GNU software. He has access to our source code, and I had also previously sent him the output of license checker so he really should have been able to answer this himself.

NPM License Checker

I don't care whether it's all in one file or in a dozen files, but I want all of that information to be available programmatically in a text file (unlike in a readme or on Github) in a standardized location in a project.

In that respect, package.json is a strict win. Your lack of willingness to use `git blame` to see why you added a line, or lack of reasonable git comments, is not to be blamed on the file.

Complexity is unavoidable. How could you write a tool like license-checker [1] for a Go-based project without having license information in a standardized location? Without the scripts section, how can you create a tool like husky [2] that automatically installs git hooks for a project? Every single part of package.json is there for a good reason; at best you could argue that putting some of it in other files would be aesthetically superior, but that's just bikeshedding.

Complexity isn't de facto bad. Some complexity is required if you want a certain level of functionality to become available. Deno (and Go) are slowly accumulating that "cruft" as people realize that those functions are actually useful or even critical to a mature ecosystem.

[1] https://www.npmjs.com/package/license-checker

[2] https://www.npmjs.com/package/husky

Yes, all npm packages are supposed to have a valid SPDX license identifier, and there is an easy way to recursively check these values

For JavaScript I always used davglass/license-checker as a starting point but it's not being maintained anymore. Then I did similar things for the backend code, put everything together and sent it to the legal and security teams. At some point I thought "There must be a better way!". So, I started building sbomx about one and a half years ago. It's working fine enough to show it to the world and gather some feedback.

Check this package https://www.npmjs.com/package/license-checker

Good doctors and drivers make mistakes, too, and they still face liability for those mistakes.

I think that if your company is large enough, you should have employees, or pay someone, to mirror your dependencies and automate license checks. There are projects that do the latter already[1][2]. You can loop your lawyers in if licenses change to ensure you don't violate them. If (A)GPL code still ships in proprietary products, that's a process problem that the company needs to solve.

[1] https://github.com/dhatim/python-license-check

[2] https://github.com/davglass/license-checker

license-checker - Check licenses of your app's dependencies.

If you don't know what licenses you're currently using, I suggest the license-checker NPM tool.

Also, your IT dept is not entirely without concern here, you should be ensuring that you're not violating any open source licenses in your project, and be using something like https://www.npmjs.com/package/license-checker or an equivalent license checking service in your project language to ensure that everything is kosher

I picked up standard[1] a while back for this reason, I don't want to have to think about it. It works fine, I have no complaints (took me a while to get used to not using semi-colons but now I prefer it) Same reason I use `cargo fmt` as well.

[1] https://standardjs.com/

# question 1: ? How would you like to use ESLint? … To check syntax only To check syntax and find problems ❯ To check syntax, find problems, and enforce code style # question 2: ? What type of modules does your project use? … ❯ JavaScript modules (import/export) CommonJS (require/exports) None of these # question 3: ? Which framework does your project use? … ❯ React Vue.js None of these # question 4 (select "No", because we won't add TypeScript support for this project): ? Does your project use TypeScript? › No / Yes # question 5: ? Where does your code run? … Browser ✔ Node # question 6: ? How would you like to define a style for your project? … ❯ Use a popular style guide Answer questions about your style Inspect your JavaScript file(s) # question 7 (we'll rely on Airbnb's JavaScript style guide here): ? Which style guide do you want to follow? … ❯ Airbnb: https://github.com/airbnb/javascript Standard: https://github.com/standard/standard Google: https://github.com/google/eslint-config-google # question 8: ? What format do you want your config file to be in? … JavaScript YAML ❯ JSON # the final prompt here is where eslint will ask you if you want to install all the necessary dependencies. Select "Yes" and hit enter: Checking peerDependencies of eslint-config-airbnb@latest The config that you have selected requires the following dependencies: eslint-plugin-react@^7.21.5 eslint-config-airbnb@latest eslint@^5.16.0 || ^6.8.0 || ^7.2.0 eslint-plugin-import@^2.22.1 eslint-plugin-jsx-a11y@^6.4.1 eslint-plugin-react-hooks@^4 || ^3 || ^2.3.0 || ^1.7.0 ? Would you like to install them now with npm? › No / Yes

A Thin JavaScript Document Storage with Middleware Stack

https://github.com/standard/standard/issues/384

For example, if you use https://standardjs.com/ - it will error on your second code snippet and if you ask it for an autofix - it will transfer the minus sign to the first line.

In comparison, JavaScript doesn't have a strict coding standard, although it does have widely accepted code style guides like the Airbnb JavaScript Style Guide and the JavaScript Standard Style. These guides provide recommendations for code formatting and naming conventions, but they are not as strictly enforced as the Java coding standard.