Use authoring tool like Dist::Zilla, Milla, and Minilla to generate correct provides.

Error: lib/Build/Hopen/TEMPLATE.pm

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: Build::Hopen, Build::Hopen::App, Build::Hopen::AppUtil, Build::Hopen::BuildSystemGlobals, Build::Hopen::G::CollectOp, Build::Hopen::G::DAG, Build::Hopen::G::Entity, Build::Hopen::G::FilesOp, Build::Hopen::G::Goal, Build::Hopen::G::GraphBuilder, Build::Hopen::G::Link, Build::Hopen::G::Node, Build::Hopen::G::Op, Build::Hopen::G::Runnable, Build::Hopen::Gen, Build::Hopen::Gen::Make, Build::Hopen::H, Build::Hopen::HopenFileKit, Build::Hopen::Phase::Check, Build::Hopen::Phase::Gen, Build::Hopen::Phases, Build::Hopen::Scope, Build::Hopen::Scope::Environment, Build::Hopen::Scope::Hash, Build::Hopen::Scope::Inputs, Build::Hopen::Scope::Overrides, Build::Hopen::T::Gnu, Build::Hopen::T::Gnu::C, Build::Hopen::Tool, Build::Hopen::Toolchain, Build::Hopen::Util::Data, Build::Hopen::Util::Filename, Build::Hopen::Util::NameSet

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.