◈ ArtifactScan
← Projects
/
Argus · 2026-07-02
Argus · 2026-07-02
https://github.com/Uninett/Argus ↗
51
%
✓
26
/53
Passed
⚠
20
/53
Warnings
✕
6
/53
Failures
—
0
/53
Skipped
ℹ
1
/53
Info
📁
ARTEFACTS
3/7
📖
README
11/29
⚖
LICENSE
3/4
👥
AUTHORS
0/1
📝
CHANGELOG
8/9
🤝
CONTRIBUTING
0/1
💾
FILES
2/2
3/7
passed
4 warnings
README file found: README.md
LICENSE file found: LICENSE
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.
11/29
passed
5 failed
13 warnings
1 info
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."
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/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.
Compatibility signals detected
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.
Documentation signals detected
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.
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.
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.
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.
Broken links detected in README: htmlcov/index.html
💡 How to fix
📄 README
Suggested fix
Check all relative links in README.md and ensure the referenced files exist in the repository.
3/4
passed
1 warnings
LICENSE file has adequate length (35149 characters)
ScanCode detected licenses: GENERIC-CLA, GPL-3.0, MIT, UNKNOWN-LICENSE-REFERENCE
LICENSE file correctly declares GPL-3.0
Licenses found in code but not declared in LICENSE: GENERIC-CLA, MIT, UNKNOWN-LICENSE-REFERENCE
💡 How to fix
📄 LICENSE
Suggested fix
Document all third-party licences found in the codebase in the LICENSE file.
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.
8/9
passed
1 warnings
Project name detected in CHANGELOG
📄 CHANGELOG.md
Version entries detected in CHANGELOG
📄 CHANGELOG.md
Version + date pattern detected in CHANGELOG
📄 CHANGELOG.md
Added section detected in CHANGELOG
📄 CHANGELOG.md
Changed section detected in CHANGELOG
📄 CHANGELOG.md
Deprecated section detected in CHANGELOG
📄 CHANGELOG.md
Removed section detected 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.
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)