ssa Deleted
Kwalitee Issues
- extracts_nicely
-
Pack the distribution with a proper command such as "make dist" and "./Build dist", or use a distribution builder such as Dist::Zilla, Dist::Milla, Minilla.
Error: More than one top directories are found: Makefile.PL;t;README;lib
- no_pax_headers
-
If you use Mac OS X >= 10.6, use gnu tar (/usr/bin/gnutar) to avoid PAX headers. It's also important to rename (shorten) long file names (>= 100 characters) in the distribution.
Error: PaxHeader/lib,PaxHeader/lib,lib/PaxHeader/Parse,lib/PaxHeader/Parse,lib/Parse/PaxHeader/SSA.pm,lib/Parse/PaxHeader/SSA.pm,PaxHeader/t,PaxHeader/t,t/PaxHeader/data,t/PaxHeader/data,t/data/PaxHeader/test.ass,t/data/PaxHeader/test.ass,t/PaxHeader/00_compile.t,t/PaxHeader/00_compile.t,PaxHeader/Makefile.PL,PaxHeader/Makefile.PL,PaxHeader/README,PaxHeader/README
- has_manifest
-
Add a MANIFEST to the distribution. Your buildtool should be able to autogenerate it (eg "make manifest" or "./Build manifest")
- has_meta_yml
-
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
- has_changelog
-
Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.
- has_version
-
Add a version number to the packed distribution. Or use a buildtool ('make dist' or 'Build dist')
- has_proper_version
-
Remove all letters from the version number. If you want to mark a release as a developer release, use the scheme 'Module-1.00_01'
- manifest_matches_dist
-
Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually.
Error: Cannot find MANIFEST in dist.
- has_abstract_in_pod
-
Provide a short description in the NAME section of the pod (after the module name followed by a hyphen) at least for the main module of this distribution.
- use_strict
-
Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.
Error: Parse::SSA
- main_module_version_matches_dist_version
-
Make sure that the main module name and version are the same of the distribution.
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: lib/Parse/SSA.pm -- Around line 6: =pod directives shouldn't be over one line long! Ignoring all 3 lines of content
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- meta_yml_has_license
-
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
- 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.
Modules
Name | Abstract | Version | View |
---|---|---|---|
Parse::SSA | 1.0 | metacpan |