Opera Software AS (OPERA)

Showing the uploads of OPERA

• 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
Cache-Memcached-Mock		OPERA	2013-08-12T07:51:31	GitHub	RT	Add CI	perl_5	678	2	0	0	79.75	Add dashboard	96.88	0
Arepa		OPERA	2013-05-30T12:03:45	Add repo	Add repo	Add repo		275	0	0	0	56.83	Add dashboard	93.75	0
Net-SMS-RoutoMessaging		OPERA	2013-05-22T11:51:33	GitHub	RT	Add CI	bsd	3	0	0	0	43.42	Add dashboard	100.00	0
Net-SMS-Mach		OPERA	2011-08-15T06:51:33	GitHub	RT	Add CI	bsd	459	0	0	1	44.83	Add dashboard	100.00	0
Parse-Debian-PackageDesc		OPERA	2010-08-19T10:32:36	Add repo	Add repo	Add repo		1320	300	0	61	90.91	Add dashboard	93.75	1
Migraine		OPERA	2009-11-17T10:16:51	Add repo	Add repo	Add repo		0	0	2	0	15.41	Add dashboard	90.62	1

Statistics

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