Packages / openSUSE Leap 15.6 / Development/Libraries/Perl / perl-JSON-Any

Package: perl-JSON-Any (1.39-bp156.3.1)

(DEPRECATED) Wrapper Class for the various JSON classes

This module tries to provide a coherent API to bring together the various JSON modules currently on CPAN. This module will allow you to code to any JSON API and have it work regardless of which JSON module is actually installed. use JSON::Any; my $j = JSON::Any->new; $json = $j->objToJson({foo=>'bar', baz=>'quux'}); $obj = $j->jsonToObj($json); or $json = $j->encode({foo=>'bar', baz=>'quux'}); $obj = $j->decode($json); or $json = $j->Dump({foo=>'bar', baz=>'quux'}); $obj = $j->Load($json); or $json = $j->to_json({foo=>'bar', baz=>'quux'}); $obj = $j->from_json($json); or without creating an object: $json = JSON::Any->objToJson({foo=>'bar', baz=>'quux'}); $obj = JSON::Any->jsonToObj($json); On load, JSON::Any will find a valid JSON module in your @INC by looking for them in this order: Cpanel::JSON::XS JSON::XS JSON::PP JSON JSON::DWIW And loading the first one it finds. You may change the order by specifying it on the 'use JSON::Any' line: use JSON::Any qw(DWIW XS CPANEL JSON PP); Specifying an order that is missing modules will prevent those module from being used: use JSON::Any qw(CPANEL PP); # same as JSON::MaybeXS This will check in that order, and will never attempt to load the JSON::XS manpage, the JSON.pm/JSON manpage, or the JSON::DWIW manpage. This can also be set via the '$ENV{JSON_ANY_ORDER}' environment variable. the JSON::Syck manpage has been deprecated by its author, but in the attempt to still stay relevant as a "Compatibility Layer" JSON::Any still supports it. This support however has been made optional starting with JSON::Any 1.19. In deference to a bug request starting with JSON 1.20, the JSON::Syck manpage and other deprecated modules will still be installed, but only as a last resort and will now include a warning. use JSON::Any qw(Syck XS JSON); or $ENV{JSON_ANY_ORDER} = 'Syck XS JSON'; At install time, JSON::Any will attempt to install the JSON::PP manpage as a reasonable fallback if you do not appear have *any* backends installed on your system. WARNING: If you call JSON::Any with an empty list use JSON::Any (); It will skip the JSON package detection routines and will die loudly that it couldn't find a package.

Other Packages Related to perl-JSON-Any:

  • dep: perl(:MODULE_COMPAT_5.26.1)

    Package not available

Download perl-JSON-Any

ArchitecturePackage sizeInstalled sizeFilesPackage
noarch32 KiB58 KiBlist of filesDownload

Package file paths (9)

Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.

  • /usr/lib/perl5/vendor_perl/5.26.1/JSON
  • /usr/lib/perl5/vendor_perl/5.26.1/JSON/Any.pm
  • /usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi
  • /usr/share/doc/packages/perl-JSON-Any
  • /usr/share/doc/packages/perl-JSON-Any/Changes
  • /usr/share/doc/packages/perl-JSON-Any/CONTRIBUTING
  • /usr/share/doc/packages/perl-JSON-Any/LICENSE
  • /usr/share/doc/packages/perl-JSON-Any/README
  • /usr/share/man/man3/JSON::Any.3pm.gz

Field source: openSUSE Leap 15.6 OSS

Use this package

OpenFactory can boot this operating system in a browser VM, or start a build that includes the native package name from this record.

Versions, suites, and repositories

Each row is recorded package-index metadata for one version, architecture, suite, and repository. Names, URLs, and sizes are source-reported; a link is a potentially mutable retrieval location, not an OpenFactory redistribution claim or proof that OpenFactory retained the artifact bytes.

VersionReleaseArchitectureRepositoryPackage sizeInstalled sizePublisher repository artifact
1.39-bp156.3.1leap-15.6 / ossnoarchopenSUSE Leap 15.6 · OSS · multi-architecture32 KiB58 KiBnoarch/perl-JSON-Any-1.39-bp156.3.1.noarch.rpm

Field source: openSUSE Leap 15.6 OSS

Known vulnerabilities

Matching against OpenFactory catalog package versions is in progress.

Last synced:

[CVE catalog]

Checksums

Repository signatures authenticate metadata. Artifact hashing is recorded separately. Neither establishes package safety.

1.39-bp156.3.1 / noarchObserved Sep 1, 2026sha512 634ef361cafb…247dddd8Source-reported digest

Metadata observed; artifact bytes were not independently fetched or hashed by this catalog import. The digest below is source-reported.

Source-reported digest (sha512): 634ef361cafb56ffd96ca19efd77d68c79c2a613bf4468fda22335f65cdcc43f521e4dd13a50a07127803f0ef916ba9646045f10e3e12541a2b492dc247dddd8

Field source: openSUSE Leap 15.6 OSS

Sources

  • Authoritative source; repository metadata signature verified

    Signature evidence

    leap-15-6-oss-multiarch:ca2653101b9afba6656aea529109ba0c0f1ca1a92aa8614e7c887fda5264c230

    Repository-signature verification record
    Signed-object SHA-256
    ca2653101b9afba6656aea529109ba0c0f1ca1a92aa8614e7c887fda5264c230
    Signer fingerprint
    AD485664E901B867051AB15F35A2F86E29B700A4
    Keyring revision
    opensuse-project-signing-key.asc
    SHA-256 b5745739ebfb95b25b8e810f9bcb847fe750ccda598bd85f02f0e974599a6d7e
    Tool and policy
    gpgv (GnuPG) 2.4.9
    openfactory-software-catalog-signature-v1
    Verification time
    Sep 1, 2026
    Repository metadata hash linkage
    Result
    Recorded as verified; digest details unavailable