Skip to main content

licomp-aflc

Implementation of Licomp using OSADL's matrix

Licomp Osadl provides compatibility data:

  • between an Open Source outbound license and inbound Open Source licenses
  • when copying code from one Open Source component to another and
  • the Open Source components are unmodified

Licomp Osadl uses OSADL's license matrix, part of OSADL's license checklist

Introduction

Licomp Osadl implements the Licomp api for communication with the Licomp resources. For a better understanding of Licomp we suggest you read:

The various licomp resources below can be accessed as a group by:

Licomp is used be the following compatibility resources:

Using Licomp Osadl

Since Licomp Osadl implements Licomp we refer to the Licomp guides (both cli and python api).

Command line interface

See Licomp Comand Line Interface

Note: the commmad line program for Licomp Osadl is called licomp-aflc.

Python module

See Licomp Python API

Installing Licomp Osadl

From pypi.org

Licomp Osadl is available via pypi.org at: https://pypi.org/project/licomp-aflc/.

To install, simply do the following:

$ pip install licomp-aflc

From github

Installing from github assumes you already have pip installed.

$ git clone https://github.com/hesa/licomp-aflc
$ pip install -r requirements.txt
$ pip install -r requirements-dev.txt
$ pip install .

Metadata

Release files for licomp-aflc 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for licomp-aflc 0.1.1
File Size Uploaded Provenance Actions
licomp_aflc-0.1.1.tar.gz 23.6 kB Without provenance Details for licomp_aflc-0.1.1.tar.gz

Release files / licomp_aflc-0.1.1.tar.gz

Download URL licomp_aflc-0.1.1.tar.gz
Size 23.6 kB
Tags Source
SHA-256 checksum
How to use checksums
feedcd7c9474475e390c6563e7ce3b61afc3eec2883fb90169855e6f805736db
BLAKE2b-256 checksum
How to use checksums
c57c79e4c69d446d554fb2cdc2398210dfe066de849cd5391ffb775455fb9b94
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Security for licomp-aflc 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page