Johan Lodin (LODIN)

Showing the uploads of LODIN

• 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
Time-Consts		LODIN	2017-02-11T14:34:43	Add repo	Add repo	Add repo		3	0	0	0	95.56	Add dashboard	100.00	0
Sub-Recursive		LODIN	2015-07-18T06:39:35	Add repo	Add repo	Add repo		7	0	0	0	100.00	Add dashboard	100.00	3
List-Extract		LODIN	2008-07-03T19:17:43	Add repo	Add repo	Add repo		620	0	1	1	100.00	Add dashboard	100.00	0
Sub-Prepend		LODIN	2008-07-03T19:02:18	Add repo	Add repo	Add repo		2033	0	1	1	100.00	Add dashboard	100.00	3
Regexp-Exhaustive		LODIN	2008-01-06T06:03:45	Add repo	Add repo	Add repo		1304	18	2	2	99.00	Add dashboard	100.00	1
Text-Outdent		LODIN	2005-07-23T10:00:48	Add repo	Add repo	Add repo		2904	0	1	0	86.11	Add dashboard	100.00	2
Sub-Curry		LODIN	2005-02-28T15:28:36	Add repo	Add repo	Add repo		745	0	1	0	84.16	Add dashboard	96.88	2

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% )