If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.

Add a META.json to the distribution. Your buildtool should be able to autogenerate it.

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.

Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.

Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.

Error: X3D, X3D::Array, X3D::ArrayField, X3D::ArrayHash, X3D::BaseFieldTypes::Scalar, X3D::BaseFieldTypes::Vector, X3D::BaseNode, X3D::Callbacks, X3D::Component, X3D::Components::Core, X3D::Components::Core::BindableNode, X3D::Components::Core::ChildNode, X3D::Components::Core::InfoNode, X3D::Components::Core::MetadataObject, X3D::Components::Core::Node, X3D::Components::Core::Nodes::MetadataDouble, X3D::Components::Core::Nodes::MetadataFloat, X3D::Components::Core::Nodes::MetadataInteger, X3D::Components::Core::Nodes::MetadataSet, X3D::Components::Core::Nodes::MetadataString, X3D::Components::Core::Nodes::WorldInfo, X3D::Components::Core::PrototypeInstance, X3D::Components::Core::SensorNode, X3D::Constants, X3D::Environment, X3D::ExecutionContext, X3D::Field, X3D::FieldDefinition, X3D::FieldHelper, X3D::FieldSet, X3D::FieldTypes, X3D::FieldTypes::MFBool, X3D::FieldTypes::MFColor, X3D::FieldTypes::MFColorRGBA, X3D::FieldTypes::MFDouble, X3D::FieldTypes::MFFloat, X3D::FieldTypes::MFImage, X3D::FieldTypes::MFInt32, X3D::FieldTypes::MFNode, X3D::FieldTypes::MFRotation, X3D::FieldTypes::MFString, X3D::FieldTypes::MFTime, X3D::FieldTypes::MFVec2d, X3D::FieldTypes::MFVec2f, X3D::FieldTypes::MFVec3d, X3D::FieldTypes::MFVec3f, X3D::FieldTypes::MFVec4d, X3D::FieldTypes::MFVec4f, X3D::FieldTypes::SFBool, X3D::FieldTypes::SFColor, X3D::FieldTypes::SFColorRGBA, X3D::FieldTypes::SFDouble, X3D::FieldTypes::SFFloat, X3D::FieldTypes::SFImage, X3D::FieldTypes::SFInt32, X3D::FieldTypes::SFNode, X3D::FieldTypes::SFRotation, X3D::FieldTypes::SFString, X3D::FieldTypes::SFTime, X3D::FieldTypes::SFVec2d, X3D::FieldTypes::SFVec2f, X3D::FieldTypes::SFVec3d, X3D::FieldTypes::SFVec3f, X3D::FieldTypes::SFVec4d, X3D::FieldTypes::SFVec4f, X3D::Generator, X3D::Hash, X3D::Math, X3D::Message, X3D::Namespace, X3D::Object, X3D::Package, X3D::ParentHash, X3D::Parse::Concept, X3D::Parse::Double, X3D::Parse::FieldDescription, X3D::Parse::FieldValue, X3D::Parse::Float, X3D::Parse::Id, X3D::Parse::Int32, X3D::Parse::String, X3D::Parser, X3D::RegularExpressions, X3D::Route, X3D::Scene, X3D::Symbols, X3D::Tie::ArrayLength, X3D::Tie::Field, X3D::Tie::Value::Array, X3D::Tie::Value::BaseNodeArray, X3D::Tie::Value::Rotation, X3D::Tie::Value::Vector, X3D::Tie::WeakHash, X3D::Universal, X3D::Values, X3D::Values::Color, X3D::Values::ColorRGBA, X3D::Values::Image, X3D::Values::Rotation, X3D::Values::Vec2, X3D::Values::Vec3, X3D::Values::Vec4, X3D::Values::Vector

Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).

Error: 0.001,0.002,0.003,0.005,0.006,0.009,0.01,0.011,0.012,0.013,0.014,0.015,0.016

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.

Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).

This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.

Add SECURITY(.pod|md). See Software::Security::Policy.

Add SECURITY(.pod|md) and add a contact address. See Software::Security::Policy.

Add CONTRIBUTING(.pod|md). See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.