Clipland (CLIPLAND)

Showing the uploads of CLIPLAND

• 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
Text-NSR		CLIPLAND	2023-03-20T22:40:30	Add repo	Add repo	Add repo		556	0	0	0	94.34	Add dashboard	96.88	0
Net-Twitch-API		CLIPLAND	2022-03-07T19:20:56	GitHub	Add bugtracker	Add CI	artistic_2	278	0	0	0	56.25	Add dashboard	96.88	0
Image-Animated-JPEG		CLIPLAND	2019-06-19T20:30:00	GitHub	Add bugtracker	Add CI	open_source	396	0	1	0	68.74	Add dashboard	100.00	0
Wrangler		CLIPLAND	2015-02-16T19:07:41	GitHub	Add bugtracker	Add CI	restricted	0	0	0	7	14.63	Add dashboard	100.00	0
Fuse-TagLayer		CLIPLAND	2013-12-09T17:43:12	Add repo	Add repo	Add repo		34	0	0	0	83.33	Add dashboard	96.88	0
Fuse-PerlSSH-FS		CLIPLAND	2013-02-28T15:07:10	GitHub	Add bugtracker	Add CI	open_source					90.00	Add dashboard	100.00	0

Statistics

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