Troels Liebe Bentsen (TLBDK)

Showing the uploads of TLBDK

• 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
Privileges-Drop		TLBDK	2011-09-20T11:14:19	Add repo	Add repo	Add repo		8	0	0	0	24.18	Add dashboard	96.88	5
Sys-Prctl		TLBDK	2011-09-20T10:57:18	Add repo	Add repo	Add repo		0	4	0	2	84.38	Add dashboard	100.00	3
IO-EventMux		TLBDK	2009-04-17T23:05:36	Add repo	Add repo	Add repo		118	119	74	0	-	Add dashboard	96.88	1
Timeout-Queue		TLBDK	2009-04-15T22:43:00	Add repo	Add repo	Add repo		463	193	1	0	90.85	Add dashboard	100.00	0
IO-EventMux-Socket-MsgHdr		TLBDK	2009-03-22T21:55:26	Add repo	Add repo	Add repo		309	243	181	1	60.57	Add dashboard	100.00	2
IO-Buffered		TLBDK	2009-03-22T21:54:00	Add repo	Add repo	Add repo		389	159	81	1	78.62	Add dashboard	100.00	0
RPC-Async		TLBDK	2007-12-30T14:26:25	Add repo	Add repo	Add repo		79	33	3	4	-	Add dashboard	100.00	0
RPM-Header-PurePerl		TLBDK	2006-12-08T14:18:28	Add repo	Add repo	Add repo		3	0	0	0	58.16	Add dashboard	90.62	0

Statistics

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