(KFLY) on CPAN Digger

()

Showing the uploads of

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	Author	Date	VCS	Issues	CI	Licenses	Coverage	Dashboard	Kwalitee
Syntax-Keyword-Assert	KFLY	2024-12-18T09:01:32	GitHub	GitHub	GitHub Actions	perl_5	-	Add dashboard	100.00
kura	KFLY	2024-12-16T00:45:23	GitHub	GitHub	GitHub Actions	perl_5	-	Add dashboard	100.00
Result-Simple	KFLY	2024-11-27T01:19:57	GitHub	GitHub	GitHub Actions	perl_5	-	Add dashboard	100.00

Name

MetaCPAN

Author

Date

VCS

Issues

Licenses

CT Pass

CT Fail

CT Unknown

CT NA

Coverage