()

Showing the uploads of

Having the link to your public Version Control System (VCS) in the META files help others to contribute to your code.
Having an explicit link to your bugtracker/issues in the META file help people know where to submit bug reports.
Having Continuous Integration (CI) configured helps the author catch regression and platform incompability much faster.
Having license information in the META files can help people automatically verify that they use only approved licenses.
Having your own CPAN Dashboard is cool.
CT Stands for CPAN Testers
No means the author does not have public VCS and does not want to have one or that the author is not interested in CI (for at least some of the modules).

Total: 7

Name	MetaCPAN	Author	Date	VCS	Issues	CI	Licenses	CT Pass	CT Fail	CT Unknown	CT NA	Coverage	Dashboard	Kwalitee	Reverse
Crypt-OpenSSL-PKCS10		TIMLEGGE	2025-01-22T10:42:30	GitHub	RT	GitHub Actions	perl_5					-	Add dashboard	??	0
Software-Security-Policy		TIMLEGGE	2025-01-15T01:57:18	GitHub	GitHub	Add CI	perl_5					-	Add dashboard	100.00	0
XML-Enc		TIMLEGGE	2024-12-28T13:12:10	Add repo	Add repo	Add repo						-	Add dashboard	100.00	0
Crypt-OpenPGP		TIMLEGGE	2024-12-22T23:21:31	GitHub	Add bugtracker	GitHub Actions	perl_5					-	Add dashboard	96.88	0
Crypt-DSA		TIMLEGGE	2024-12-04T14:50:02	GitHub	Add bugtracker	Add CI	perl_5					-	Add dashboard	100.00	1
Convert-PEM		TIMLEGGE	2024-12-03T03:43:21	GitHub	Add bugtracker	Add CI	perl_5					-	Add dashboard	100.00	3
IO-Compress-Brotli		TIMLEGGE	2024-11-30T18:35:29	GitHub	Add bugtracker	GitHub Actions Travis	perl_5					-	Add dashboard	96.88	0

Statistics

Total: 7
Has VCS: 6 ( 85% )
- GitHub: 6
- GitLab:
Has CI: 3 ( 42% )
- GitHub Actions: 3
- Jenkins: 0
- Azure Pipeline: 0
- Travis-CI: 1
- CircleCI: 0
- Appveyor: 0
- GitLab Pipeline: 0
- Bitbucket Pipelines: 0
Has Bugz: 2 ( 28% )