◈ ArtifactScan
← Projects
/
nextgen-looking-glass · 2026-04-21
nextgen-looking-glass · 2026-04-21
https://gitlab.software.geant.org/geant-swd/lg/nextgen-looking-glass ↗
23
%
✓
12
/52
Passed
⚠
31
/52
Warnings
✕
9
/52
Failures
—
0
/52
Skipped
ℹ
0
/52
Info
📁
ARTEFACTS
3/7
📖
README
2/29
⚖
LICENSE
3/3
👥
AUTHORS
0/1
📝
CHANGELOG
2/9
🤝
CONTRIBUTING
0/1
💾
FILES
2/2
3/7
passed
4 warnings
README file found: README.md
LICENSE file found: LICENSE.txt
NOTICE file not found
💡 How to fix
Suggested fix
Create a NOTICE file if your licence requires it (e.g. Apache-2.0). List third-party components, their licences, and required attribution notices.
COPYRIGHT file not found
💡 How to fix
Suggested fix
Create a COPYRIGHT file listing copyright holders, years, and organisation (e.g. "Copyright © 2024 GÉANT Association").
AUTHORS file not found
💡 How to fix
Suggested fix
Create an AUTHORS file listing the main developers and contributors, their roles, affiliations and optionally contact details.
CHANGELOG file found: CHANGELOG.md
CONTRIBUTING file not found
💡 How to fix
Suggested fix
Create a CONTRIBUTING.md explaining how to report bugs, suggest features, and submit pull requests.
2/29
passed
7 failed
20 warnings
Project name detected in README
No clear copyright one-liner detected in README
💡 How to fix
📄 README
Suggested fix
Add a short copyright line near the top of README.md, e.g. "Copyright © 2024 GÉANT Association. Licensed under MIT."
No explicit lifecycle/status detected in README
💡 How to fix
📄 README
Suggested fix
Add a project status badge or line indicating the lifecycle stage, e.g. "Status: Stable", "Status: Beta".
No tags/keywords detected in README
💡 How to fix
📄 README
Suggested fix
Add a "Tags:" or "Keywords:" line in README.md to help discoverability.
No clear version indication in README
💡 How to fix
📄 README
Suggested fix
Add the current stable version near the top of README.md, e.g. "Version: 2.1.0" or a shields.io release badge.
Licence one-liner/link not detected in README
💡 How to fix
📄 README
Suggested fix
Add a one-line licence statement with a link, e.g. "Licensed under the [MIT Licence](LICENSE)."
No clear description/overview in README
💡 How to fix
📄 README
Suggested fix
Add an "Overview" or "About" section clearly explaining what the project does, who it is for, and what problem it solves.
No features section in README
💡 How to fix
📄 README
Suggested fix
Add a "Features" section listing the key functionalities as a bullet list.
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.
No requirements section in README
💡 How to fix
📄 README
Suggested fix
Add a "Requirements" section listing system dependencies, runtime versions, and hardware requirements.
No installation section in README
💡 How to fix
📄 README
Suggested fix
Add an "Installation" section with step-by-step setup instructions.
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.
No branch/tagging conventions in README
💡 How to fix
📄 README
Suggested fix
Add a section describing your branching strategy, tagging conventions, and release process.
No troubleshooting/FAQ in README
💡 How to fix
📄 README
Suggested fix
Add a "Troubleshooting" or "FAQ" section addressing common issues.
No support info in README
💡 How to fix
📄 README
Suggested fix
Add a "Support" section with links to the issue tracker, mailing list, or contact email.
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.
No authors mention in README
💡 How to fix
📄 README
Suggested fix
Add an "Authors" section or link to the AUTHORS file.
No contributing guidance in README
💡 How to fix
📄 README
Suggested fix
Add a "Contributing" section or link to CONTRIBUTING.md.
No funding info in README
💡 How to fix
📄 README
Suggested fix
Add a "Funding" section mentioning the funding source, grant agreement number, and programme.
No acknowledgements in README
💡 How to fix
📄 README
Suggested fix
Add an "Acknowledgements" section thanking third-party projects, partners, or contributors.
README missing dependencies section (manifests exist in repo)
💡 How to fix
📄 README
Suggested fix
Add a "Dependencies" section listing runtime dependencies with versions and licences, or link to NOTICE.
No tools indicators in README
📄 README
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.
No COPYRIGHT reference in README
💡 How to fix
📄 README
Suggested fix
Add a "Copyright" line referencing the COPYRIGHT file and listing copyright years and holders.
All README local links are valid
3/3
passed
LICENSE file has adequate length (1094 characters)
ScanCode detected licenses: MIT
LICENSE file correctly declares MIT
0/1
passed
1 warnings
Not in AUTHORS file or README
💡 How to fix
Suggested fix
Create an AUTHORS file or add an "Authors" section to README.md.
2/9
passed
1 failed
6 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
No Added section in CHANGELOG
💡 How to fix
📄 CHANGELOG.md
Suggested fix
Add an "### Added" subsection listing new features in each release.
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
No Fixed section in CHANGELOG
💡 How to fix
📄 CHANGELOG.md
Suggested fix
Add a "### Fixed" subsection listing bug fixes.
No Security section in CHANGELOG
💡 How to fix
📄 CHANGELOG.md
Suggested fix
Add a "### Security" subsection when security vulnerabilities were addressed.
0/1
passed
1 failed
Not in CONTRIBUTING file or README
💡 How to fix
Suggested fix
Create a CONTRIBUTING.md or add a "Contributing" section to README.md.
2/2
passed
No binary files detected
No large files detected (>= 10485760 bytes)