Ash Berlin (ASH)

Showing the uploads of ASH

• 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
WWW-Mechanize-TreeBuilder		ASH	2014-10-27T10:20:33	GitHub	GitHub	Add CI	perl_5	1871	7	1	0	50.00	Add dashboard	93.75	3
TryCatch		ASH	2013-03-22T07:49:45	GitHub	Add bugtracker	Add CI	perl_5	8482	41	11	4	83.33	Add dashboard	96.88	31
Catalyst-Model-File		ASH	2011-12-08T20:46:36	GitHub	Add bugtracker	Add CI	perl_5	774	27	5	1	83.48	Add dashboard	96.88	2
Class-Discover		ASH	2010-06-15T14:26:22	Add repo	Add repo	Add repo		4749	150	9	1	85.44	Add dashboard	100.00	8
Module-Install-ProvidesClass		ASH	2010-03-05T17:53:52	Add repo	Add repo	Add repo		297	5	155	0	-	Add dashboard	100.00	0
FormValidator-Simple-Plugin-Trim		ASH	2007-09-28T19:59:11	Add repo	Add repo	Add repo		460	0	5	1	79.07	Add dashboard	90.62	0

Statistics

• Total: 6
• Has VCS: 3 ( 50% )
• - GitHub: 3
• - 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: 1 ( 16% )