faraco (FARACO)

Showing the uploads of FARACO

• 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-Github-Email		FARACO	2018-08-31T03:49:31	GitHub	GitHub	Add CI	mit	688	0	0	0	46.30	Add dashboard	96.88	0
WebService-Gitter		FARACO	2018-01-18T06:20:48	GitHub	GitHub	Add CI	mit	435	0	0	0	10.48	Add dashboard	96.88	0
WebService-Pixabay		FARACO	2018-01-17T13:44:08	GitHub	GitHub	Add CI	mit	428	0	0	0	12.68	Add dashboard	96.88	0
App-TinyID		FARACO	2018-01-15T03:31:11	GitHub	GitHub	Add CI	mit	605	0	0	2	-	Add dashboard	96.88	0
App-Pastebin-Create2		FARACO	2017-01-16T17:40:01	GitHub	GitHub	Add CI	perl_5	381	0	0	1	-	Add dashboard	??	0
App-LWP-Online		FARACO	2017-01-16T17:39:56	GitHub	GitHub	Add CI	perl_5	4	0	0	0	-	Add dashboard	100.00	0

Statistics

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