Andrew Speer (ASPEER)

Showing the uploads of ASPEER

• 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
WebDyne		ASPEER	2017-09-15T14:12:54	GitHub	Add bugtracker	Add CI	gpl_2	0	7	0	0	54.56	Add dashboard	100.00	1
WebDyne-Template		ASPEER	2011-10-01T16:20:44	Add repo	Add repo	Add repo		438	0	0	0	13.11	Add dashboard	93.75	0
WebDyne-Session		ASPEER	2011-07-16T07:03:39	Add repo	Add repo	Add repo		442	0	0	0	50.52	Add dashboard	93.75	0
WebDyne-Chain		ASPEER	2011-07-16T07:00:56	Add repo	Add repo	Add repo		650	1	0	0	19.01	Add dashboard	100.00	0
WebDyne-Install-Lighttpd		ASPEER	2011-07-16T06:59:29	Add repo	Add repo	Add repo		447	0	0	0	37.45	Add dashboard	93.75	0
WebDyne-Request-FastCGI		ASPEER	2011-07-16T06:55:24	Add repo	Add repo	Add repo		503	1	0	0	13.66	Add dashboard	93.75	0
Bundle-WebDyne		ASPEER	2010-04-11T13:34:36	Add repo	Add repo	Add repo		416	0	0	0	100.00	Add dashboard	84.38	0

Statistics

• Total: 7
• Has VCS: 1 ( 14% )
• - 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% )