◈ ArtifactScan
← Projects
/
softwarecerthub · 2026-04-21
softwarecerthub · 2026-04-21
https://gitlab.software.geant.org/software-licensing/softwarecerthub ↗
63
%
✓
44
/70
Passed
⚠
18
/70
Warnings
✕
7
/70
Failures
—
0
/70
Skipped
ℹ
1
/70
Info
📁
ARTEFACTS
7/7
📖
README
16/29
⚖
LICENSE
3/4
©
COPYRIGHT
3/4
👥
AUTHORS
3/5
📋
NOTICE
6/10
📝
CHANGELOG
4/9
💾
FILES
2/2
7/7
passed
README file found: README.md
LICENSE file found: LICENSE
NOTICE file found: NOTICE
COPYRIGHT file found: COPYRIGHT
AUTHORS file found: AUTHORS
CHANGELOG file found: CHANGELOG.md
CONTRIBUTING file found: CONTRIBUTING.md
16/29
passed
3 failed
9 warnings
1 info
Project name not clearly detected in README
💡 How to fix
📄 README
Suggested fix
Add the project name as a top-level heading (# Project Name) at the start of README.md.
Copyright statement detected in README
Project status/lifecycle detected
No tags/keywords detected in README
💡 How to fix
📄 README
Suggested fix
Add a "Tags:" or "Keywords:" line in README.md to help discoverability.
Version indication detected
Licence one-liner with link detected
Description/overview detected
Features section detected
No clear scope section in README
💡 How to fix
📄 README
Suggested fix
Add a "Scope" or "Use Cases" section describing when and how the software should (and should not) be used.
No compatibility section in README
💡 How to fix
📄 README
Suggested fix
Add a "Compatibility" section listing supported OS, browsers, versions, or integration targets.
No structure section in README
💡 How to fix
📄 README
Suggested fix
Add an "Architecture" or "Project Structure" section explaining the directory layout and main components.
Requirements detected
Installation signals detected
Usage/examples not clearly present in README
💡 How to fix
📄 README
Suggested fix
Add a "Usage" section with practical examples, command-line snippets, screenshots, or a link to a demo.
No documentation location in README
💡 How to fix
📄 README
Suggested fix
Add a "Documentation" section linking to your docs site, wiki, or docs/ folder.
Branch/tag wording detected
No troubleshooting/FAQ in README
💡 How to fix
📄 README
Suggested fix
Add a "Troubleshooting" or "FAQ" section addressing common issues.
Support/contact wording detected
No privacy policy in README
💡 How to fix
📄 README
Suggested fix
If the software processes personal data, add a "Privacy" section or link to a privacy policy.
No roadmap in README
💡 How to fix
📄 README
Suggested fix
Add a "Roadmap" section or link to a public issue tracker milestone.
Authors mentioned
Contributing detected
Funding wording detected
No acknowledgements in README
💡 How to fix
📄 README
Suggested fix
Add an "Acknowledgements" section thanking third-party projects, partners, or contributors.
DependencyParser found no dependencies in README/NOTICE sections
Tools indicators detected
No licence summary in README
💡 How to fix
📄 README
Suggested fix
Add a "Licence" section near the bottom of README.md with a short summary and link to the full LICENSE file.
COPYRIGHT reference detected
All README local links are valid
3/4
passed
1 warnings
LICENSE file has adequate length (11558 characters)
ScanCode detected licenses: APACHE-2.0, BSD-3-CLAUSE, GPL-3.0, MIT
LICENSE file correctly declares APACHE-2.0
Licenses found in code but not declared in LICENSE: BSD-3-CLAUSE, GPL-3.0, MIT
💡 How to fix
📄 LICENSE
Suggested fix
Document all third-party licences found in the codebase in the NOTICE file.
3/4
passed
1 failed
Copyright statement with year detected
📄 COPYRIGHT
GÉANT copyright mention detected
📄 COPYRIGHT
Found 2 copyright statement(s)
No EU logo file detected (eu-logo.png, eu-flag.png, etc.)
💡 How to fix
Suggested fix
Add the EU logo image file (eu-logo.png or eu-flag.png) to the repository root.
3/5
passed
1 failed
1 warnings
Project name not clearly detected in AUTHORS
💡 How to fix
📄 AUTHORS
Suggested fix
Add the project name as a heading at the top of the AUTHORS file.
GÉANT phase/WP detected
📄 AUTHORS
Found 1 email(s), 14 non-empty lines
No contributors section in AUTHORS
💡 How to fix
📄 AUTHORS
Suggested fix
Add a "Contributors" section listing people who contributed but are not primary authors.
Funding info detected
📄 AUTHORS
6/10
passed
1 failed
3 warnings
Project name not clearly detected in NOTICE
💡 How to fix
📄 NOTICE
Suggested fix
Add the project name as a heading at the top of the NOTICE file.
Copyright with year detected in NOTICE
📄 NOTICE
Licence declaration detected in NOTICE
📄 NOTICE
Authors reference detected in NOTICE
📄 NOTICE
Third-party section detected in NOTICE
📄 NOTICE
Tools mention detected in NOTICE
📄 NOTICE
No trademark wording in NOTICE
💡 How to fix
📄 NOTICE
Suggested fix
Add a trademark disclaimer if the project or its dependencies use registered trademarks.
No patent wording in NOTICE
📄 NOTICE
No acknowledgements in NOTICE
📄 NOTICE
Prior-notice wording detected in NOTICE
📄 NOTICE
4/9
passed
1 failed
4 warnings
Project name not clearly detected in CHANGELOG
💡 How to fix
📄 CHANGELOG.md
Suggested fix
Add the project name as a heading at the top of CHANGELOG.md.
Version entries detected in CHANGELOG
📄 CHANGELOG.md
Version + date pattern detected in CHANGELOG
📄 CHANGELOG.md
Added section detected in CHANGELOG
📄 CHANGELOG.md
No Changed section in CHANGELOG
💡 How to fix
📄 CHANGELOG.md
Suggested fix
Add a "### Changed" subsection describing modifications to existing functionality.
No Deprecated section in CHANGELOG
📄 CHANGELOG.md
No Removed section in CHANGELOG
📄 CHANGELOG.md
Fixed section detected in CHANGELOG
📄 CHANGELOG.md
No Security section in CHANGELOG
💡 How to fix
📄 CHANGELOG.md
Suggested fix
Add a "### Security" subsection when security vulnerabilities were addressed.
2/2
passed
No binary files detected
No large files detected (>= 10485760 bytes)