Hoe-Kit Chew (HOEKIT)

Showing the uploads of HOEKIT

• 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
GnuCash-SQLite		HOEKIT	2021-10-10T07:57:23	Add repo	Add repo	Add repo		181	0	0	4	93.33	Add dashboard	100.00	0
Function-Runner		HOEKIT	2021-05-09T07:10:57	GitHub	GitHub	Travis	perl_5	212	0	0	0	79.23	Add dashboard	100.00	0
Function-Version		HOEKIT	2021-04-22T00:57:17	GitHub	GitHub	Add CI	perl_5	140	0	0	3	92.31	Add dashboard	100.00	0
File-Edit		HOEKIT	2021-04-18T13:39:49	Add repo	Add repo	Add repo		69	0	0	0	-	Add dashboard	100.00	0
Book-Bilingual		HOEKIT	2021-04-17T05:15:27	GitHub	GitHub	Add CI	perl_5					90.95	Add dashboard	93.75	0
JSON-JSend		HOEKIT	2016-04-23T03:25:28	Add repo	Add repo	Add repo		4	0	0	0	96.92	Add dashboard	100.00	0
WWW-Mechanize-Firefox-Extended		HOEKIT	2015-05-20T03:24:15	Add repo	Add repo	Add repo		488	0	0	0	41.38	Add dashboard	100.00	0

Statistics

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