Clive Darke (CLIVE)

Showing the uploads of CLIVE

• 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
App-sh2p		CLIVE	2009-02-08T20:22:03	Add repo	Add repo	Add repo		572	3	1	10	4.65	Add dashboard	90.62	0
Win32-StreamNames		CLIVE	2009-01-13T18:14:17	Add repo	Add repo	Add repo		43	1	6	152	-	Add dashboard	93.75	0
Win32-EnvProcess		CLIVE	2008-06-29T06:44:23	Add repo	Add repo	Add repo		17	6	7	136	-	Add dashboard	93.75	0
Win32-FetchCommand		CLIVE	2008-06-17T12:52:00	Add repo	Add repo	Add repo		4	51	0	132	-	Add dashboard	93.75	0
Win32-IdentifyFile		CLIVE	2008-01-30T13:35:55	Add repo	Add repo	Add repo		37	5	6	135	-	Add dashboard	90.62	0
Win32-SearchPath		CLIVE	2004-11-17T17:48:33	Add repo	Add repo	Add repo		42	6	93	0	-	Add dashboard	84.38	0

Statistics

• Total: 6
• Has VCS: 0 ( 0% )
• - GitHub:
• - 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% )