()
Showing the uploads of
Total: 2
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CryptX |  |
MIK | 2025-05-02T21:40:16 | GitHub | GitHub |
Appveyor GitHub Actions |
perl_5 | - | Add dashboard | 100.00 | 35 | ||||
| Crypt-JWT |  |
MIK | 2025-04-27T15:02:48 | GitHub | GitHub |
Appveyor GitHub Actions |
perl_5 | - | Add dashboard | 100.00 | 8 |
Statistics
- Total: 2
- Has VCS: 2 ( 100% )
- - GitHub: 2
- - GitLab:
- Has CI: 2 ( 100% )
- - GitHub Actions: 2
- - Jenkins: 0
- - Azure Pipeline: 0
- - Travis-CI: 0
- - CircleCI: 0
- - Appveyor: 2
- - GitLab Pipeline: 0
- - Bitbucket Pipelines: 0
- Has Bugz: 2 ( 100% )