小松 大輔(Daisuke Komatsu) (TARO)

Showing the uploads of TARO

• 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).

Name	MetaCPAN	Author	Date	VCS	Issues	CI	Licenses	CT Pass	CT Fail	CT Unknown	CT NA	Coverage	Dashboard	Kwalitee	Reverse
Config-Multi		TARO	2013-03-09T15:17:58	Add repo	Add repo	Add repo		435	1	2	0	96.38	Add dashboard	96.88	1
FormValidator-LazyWay		TARO	2012-12-24T18:03:28	GitHub	Add bugtracker	Add CI	Add license	772	14	4	0	83.35	Add dashboard	87.50	0
Log-Dispatch-Colorful		TARO	2009-09-20T09:31:13	Add repo	Add repo	Add repo		0	3	0	0	38.70	Add dashboard	100.00	0
Catalyst-Controller-AllowDisable		TARO	2009-09-20T09:04:13	repository	Add bugtracker	Add CI	perl_5	2	0	0	0	70.00	Add dashboard	96.88	0
Catalyst-Plugin-Log-Colorful		TARO	2009-05-10T15:10:16	repository	Add bugtracker	Add CI	perl_5	686	7	5	0	22.09	Add dashboard	90.62	0
Template-Plugin-PwithBR		TARO	2007-05-12T13:50:33	Add repo	Add repo	Add repo		513	0	2	1	90.91	Add dashboard	100.00	0

Statistics

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