MOCK (MOCK)

Showing the uploads of MOCK

• 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
POE-Component-Client-MogileFS		MOCK	2007-05-19T00:53:07	Add repo	Add repo	Add repo		789	0	1	0	87.50	Add dashboard	100.00	1
Business-OnlinePayment-Multiplex		MOCK	2006-07-05T15:06:19	Add repo	Add repo	Add repo		318	0	1	13	100.00	Add dashboard	96.88	0
Apache2-TieBucketBrigade		MOCK	2005-08-03T22:21:06	Add repo	Add repo	Add repo		0	3	0	0	-	Add dashboard	96.88	2
Business-OnlinePayment-Exact		MOCK	2005-04-01T18:48:58	Add repo	Add repo	Add repo		0	6	3	1	87.50	Add dashboard	100.00	0
Apache-TieBucketBrigade		MOCK	2004-09-12T22:25:52	Add repo	Add repo	Add repo		1	171	212	13	-	Add dashboard	96.88	1
Business-OnlinePayment-StoredTransaction		MOCK	2004-08-13T22:02:51	Add repo	Add repo	Add repo		335	2	1	2	87.50	Add dashboard	100.00	1
Apache-SMTP		MOCK	2004-02-23T09:05:27	Add repo	Add repo	Add repo		249	0	1	0	-	Add dashboard	96.88	0

Statistics

• Total: 7
• 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% )