=> Bootstrap dependency digest>=20211023: found digest-20220214
=> Checksum BLAKE2s OK for JSON-4.10.tar.gz
=> Checksum SHA512 OK for JSON-4.10.tar.gz
===> Installing dependencies for p5-JSON-4.10nb2
=> Tool dependency mktools-[0-9]*: found mktools-20250213
=> Tool dependency cwrappers>=20150314: found cwrappers-20220403
=> Full dependency perl>=5.40.0<5.41.0: found perl-5.40.2
===> Skipping vulnerability checks.
WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found.
WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'.
===> Overriding tools for p5-JSON-4.10nb2
===> Extracting for p5-JSON-4.10nb2
===> Patching for p5-JSON-4.10nb2
===> Creating toolchain wrappers for p5-JSON-4.10nb2
===> Configuring for p5-JSON-4.10nb2
Welcome to JSON (v.4.10)
=============================

 ** BACKWARD INCOMPATIBILITY **

Since version 2.90, stringification (and string comparison) for
JSON::true and JSON::false has not been overloaded. It shouldn't
matter as long as you treat them as boolean values, but a code that
expects they are stringified as "true" or "false" doesn't work as
you have expected any more.

    if (JSON::true eq 'true') {  # now fails

    print "The result is 1 now."; # => The result is 1 now.

And now these boolean values don't inherit JSON::Boolean, either.
When you need to test a value is a JSON boolean value or not, use
JSON::is_bool function, instead of testing the value inherits
a particular boolean class or not.

Checking if your kit is complete...
Looks good
Generating a Unix-style Makefile
Writing Makefile for JSON
Writing MYMETA.yml and MYMETA.json