REUSE compliance of SAP-samples/appgyver-auth-flows

Unfortunately, github.com/SAP-samples/appgyver-auth-flows is not REUSE compliant and does not fully adopt the recommendations to make software licensing easy for humans and machines alike. Have a look at our tutorial to learn about the three simple steps to become REUSE compliant.

Badge

To add the badge to your project's README.md file, use the following snippet:

[![REUSE status](https://api.reuse.software/badge/github.com/SAP-samples/appgyver-auth-flows)](https://api.reuse.software/info/github.com/SAP-samples/appgyver-auth-flows)

Machine-readable information

The API provides machine-readable artifacts for automatic analysis.

• All information about the latest compliance check can also be accessed via a machine-parsable JSON file.
• You can gather the automatically generated SPDX SBOM in Tag:Value format, based on the reuse spdx command.

Last lint output

Commit e730c529940cc6b89992ced2e520fb8202bddc8b was checked on 21 Sep 2023 07:11:38 UTC with the following result:

The following files have no copyright and licensing information:
* .vscode/launch.json


# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: 0
* Unused licenses: 0
* Used licenses: Apache-2.0
* Read errors: 0
* files with copyright information: 93 / 94
* files with license information: 93 / 94

Unfortunately, your project is not compliant with version 3.0 of the REUSE Specification :-(