Andrew Nesbitt@andrewnez@mastodon.social

Working on a license scanner for git-pkgs, uses the scancode license rule corpus but much, much faster and less resource intensive: github.com/git-pkgs/licenses

My plan is to eventually use it to scan every version of every package with it soon.

Fast exact license matching against ScanCode's rule corpus in pure Go. - git-pkgs/licensesGitHubGitHub - git-pkgs/licenses: Fast exact license matching against ScanCode's rule corpus in pure Go.Fast exact license matching against ScanCode's rule corpus in pure Go. - git-pkgs/licenses
en
Andrew Nesbitt@andrewnez@mastodon.social

Replying to @⁨bupd@mastodon.social⁩

@bupd related issue you might want to track: github.com/git-pkgs/git-pkgs/i

Use case We generate attribution artifacts for a few hundred internal repos (Go, Ruby, npm, Python). For every resolved dependency we need the SPDX identifier and the verbatim license text (plus NO...GitHublicenses: option to emit full license text per dependency (--license-text) · Issue #294 · git-pkgs/git-pkgsUse case We generate attribution artifacts for a few hundred internal repos (Go, Ruby, npm, Python). For every resolved dependency we need the SPDX identifier and the verbatim license text (plus NO...by taltcher
Matthew Martin@mistersql@mastodon.social

Replying to @⁨andrewnez@mastodon.social⁩

@andrewnez Ah, the incredibly popular "what the heck is this license" which 80% of the time is an familiar license with slightly different name or text, the 10,000th synonym for MIT.

And missing licenses, so many are just missing.

And if you look for "hey all rights reserved, go away", never saw it in my scanning of my own deps. So just trying to find the negatives, no joy either.