GNU Savannah Evaluation for basic_unittest

Generated on Mon Oct 3 03:19:58 2016
Source: /tmp/gnu_eval.qr8lbS/./basic_unittest
Detection script version: 0.1.1

NOTE:
This auto-generated report is in alpha-stage, and may contain incorrectly detected items.
Information here should be considered as informal suggestions and guidelines.
The official GNU Savannah Hosting Requirements can be found here: https://savannah.gnu.org/register/requirements.php

A recognizable copyright statement was not detected in the following files.
A copyright statement should be of form:
Copyright YEARS NAME
An optional "(C)" and/or contact addresses can be added if you wish, such as:
Copyright (C) YEARS NAME (email)

Projects hosted on GNU Savannah must carry a copyright statement.

For more information, see How to Apply GPL License to your source code.

NOTE:
If these files contain a legally acceptable copyright statement, they are acceptable for hosting on GNU Savannah (even if this auto-generated report failed to detect it).
Revising is not a strict requirement, but is highly recommended.
A recognizable copyright statement will speed-up project approval on GNU Savannah.

Makefile
example.cpp
basic_unittest.hpp

Files without canonical license statement

The following files contains statement that is possibly a valid license, but is not the caninocal statement text. For example:
This file is part of PACKAGE and is under the same license as PACKAGE
While this is legally a valid statement, it is better to include one of the canonical full license statements.

Another common reason for mis-detection is putting the license statement at the bottom of the file (it is recommended to put the license statement at the top of the source code file, right after the copyright statement).

Projects hosted on GNU Savannah must carry a license statement.

Please consider revising the license statement, to make it easy for future users and contributers of your project.

  1. If these are source code files for your project, consider using the standard license text at the beginning of your file. For GNU licenses, See How to GNU licenses for your own software
  2. If these are supporting/auxiliary files (such as Makefile, ini files), consider adding the GNU All Permissive License.

NOTE:
If these files contain any legally acceptable license statement, they are acceptable for hosting on GNU Savannah (even if this auto-generated report failed to detect it).
Revising is not a strict requirement, but is highly recommended.
Using a standard license statement will speed-up project approval on GNU Savannah.

gpl-3.0.txt:                     GNU GENERAL PUBLIC LICENSE   The GNU General Public License is a free, copyleft  [trimmed]

Missing plain-text license file

Please include a plain-text license file, named either COPYING (for GPL-license) or LICENSE (for other licenses, such as BSD/MIT).

These are the commonly used file names, and using them will help future users and contributors for your project. If your project uses a non-standard name (e.g. license.gpl3 or bsd.txt, please consider renaming these files).

NOTE:
This is not a strict requirement, but is highly recommended.
Using a standard file name will speed-up project approval on GNU Savannah.

Summary of Licenses

License Type no. files
GPLv3-or-later 3
skipped (non-code) 1
no license detected 1

Summary of Analyzed Files

File Type no. lines Detected License Detected Copyright
gpl-3.0.txt text/plain 674 2007 Free Software Foundation, Inc. <http://fsf.org/>
Makefile text/x-makefile 63 GPLv3-or-later
README.md text/x-c skipped (non-code) skipped (non-code)
example.cpp text/x-c 89 GPLv3-or-later
basic_unittest.hpp text/x-c 155 GPLv3-or-later

END OF EVALUATION REPORT