()

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.
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: 6

Name	MetaCPAN	Author	Date	VCS	Issues	CI	Licenses	Coverage	Dashboard	Reverse
App-mdee		UTASHIRO	2026-03-17T02:31:57	GitHub	GitHub	GitHub Actions	mit	-	Add dashboard	0
Getopt-EX-termcolor		UTASHIRO	2026-03-12T02:25:15	GitHub	GitHub	GitHub Actions Travis	perl_5	-	Add dashboard	3
App-Greple-xlate		UTASHIRO	2026-03-11T07:23:06	GitHub	GitHub	GitHub Actions	perl_5	-	Add dashboard	0
Getopt-Long-Bash		UTASHIRO	2026-03-09T07:54:27	GitHub	GitHub	GitHub Actions	mit	-	Add dashboard	3
App-week		UTASHIRO	2026-03-04T08:57:17	GitHub	GitHub	GitHub Actions	perl_5	-	Add dashboard	0
App-nup		UTASHIRO	2026-03-02T06:27:11	GitHub	GitHub	GitHub Actions	mit	-	Add dashboard	1

Statistics

Total: 6
Has VCS: 6 ( 100% )
- GitHub: 6
- GitLab:
Has CI: 6 ( 100% )
- GitHub Actions: 6
- Jenkins: 0
- Azure Pipeline: 0
- Travis-CI: 1
- CircleCI: 0
- Appveyor: 0
- GitLab Pipeline: 0
- Bitbucket Pipelines: 0
Has Bugz: 6 ( 100% )