Anatoliy Lapitskiy (NUCLON)

Showing the uploads of NUCLON

• 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
Qless		NUCLON	2012-12-20T08:53:37	Add repo	Add repo	Add repo		412	21	14	0	28.94	Add dashboard	84.38	0
Catalyst-ActionRole-CheckTrailingSlash		NUCLON	2010-03-10T11:06:46	Add repo	Add repo	Add repo		504	0	0	0	100.00	Add dashboard	100.00	0
Mojo-Command-Generate-InitScript		NUCLON	2010-02-05T08:42:25	Add repo	Add repo	Add repo		13	1539	0	0	100.00	Add dashboard	100.00	0
Catalyst-ActionRole-MatchHost		NUCLON	2009-11-17T19:22:49	Add repo	Add repo	Add repo		4	0	0	0	83.33	Add dashboard	100.00	0

Statistics

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