CPANTS

Parse-Functions 0.01 Latest

has_readme: Add a README to the distribution. It should contain a quick description of your module and how to install it.
has_human_readable_license: Add a section called "LICENSE" to the documentation, or add a file named LICENSE to the distribution.
has_license_in_source_file: Add =head1 LICENSE and the text of the license to the main module in your code.

has_meta_json: Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
has_known_license_in_source_file: Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.

meta_yml_has_provides: Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.
has_separate_license_file: This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
has_security_doc: Add SECURITY(.pod|md). See Software::Security::Policy.
security_doc_contains_contact: Add SECURITY(.pod|md) and add a contact address. See Software::Security::Policy.
has_contributing_doc: Add CONTRIBUTING(.pod|md). See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.

Name	Abstract	Version	View
Parse::Functions	list all the functions in source code	0.01	metacpan
Parse::Functions::CSharp		0.01	metacpan
Parse::Functions::Java		0.01	metacpan
Parse::Functions::Perl		0.01	metacpan
Parse::Functions::Python		0.01	metacpan
Parse::Functions::Ruby		0.01	metacpan