Linux workstation

openSUSE Leap 16.0 native package

perl-JSON-Any

(DEPRECATED) Wrapper Class for the various JSON classes

Packages / openSUSE Leap 16.0 / Unspecified / perl-JSON-Any

[Source: perl-JSON-Any]

Package: perl-JSON-Any (1.400.0-bp160.1.11)

[Project overview: libjson-any-perl]

External Resources:

Homepage: [metacpan.org]

(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 JSON::XS, JSON.pm/JSON, or JSON::DWIW. This can also be set via the '$ENV{JSON_ANY_ORDER}' environment variable. JSON::Syck 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.pm 1.20, JSON::Syck 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 JSON::PP 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.42.0)

    Package not available

Download perl-JSON-Any

ArchitecturePackage SizeInstalled SizeFiles
noarch32 KiB60 KiB[list of files]

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.42.0/JSON
  • /usr/lib/perl5/vendor_perl/5.42.0/JSON/Any.pm
  • /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/README
  • /usr/share/licenses/perl-JSON-Any
  • /usr/share/licenses/perl-JSON-Any/LICENCE
  • /usr/share/man/man3/JSON::Any.3pm.gz

Field source: openSUSE Leap 16.0 OSS revision leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c

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.400.0-bp160.1.11leap-16.0 / ossnoarchopenSUSE Leap 16.0 · OSS · multi-architecture32 KiB60 KiBnoarch/perl-JSON-Any-1.400.0-bp160.1.11.noarch.rpm

Field source: openSUSE Leap 16.0 OSS revision leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c

Checksums and observation dates

For an APT source, signature verification authenticates the repository metadata chain and the Packages index containing this source-reported artifact digest. It does not certify package safety.

1.400.0-bp160.1.11 / noarchObserved Sep 1, 2026 to Sep 1, 2026

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

Source-reported sha512: 75aa98169335ac3ede0167c6bd7857e9f4ca5b9b56d75d10c9e1c1a58405b4ab859d28990ab41dbddafecd668eb9d8b7382a66cbb965f75066f0f1ddc833c5a0

Field source: openSUSE Leap 16.0 OSS revision leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c

Catalog record completeness

The completeness score measures metadata coverage, not software quality, security, compatibility, or suitability.

Summary and description
25/25
Artifact path and source digest
25/25
Dependency metadata
15/15
Package-file index
15/15
Homepage
5/5
License text
5/5
Source package or maintainer
10/10

Recorded total: 100/100

Field source: openSUSE Leap 16.0 OSS revision leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c. The cross-OS mapping is catalog-derived from the source-reported homepage; it does not establish authorship or publisher identity

Sources and provenance

Field-source links above resolve here. Each source entry names the metadata publisher, trust tier, exact snapshot revision, signature result, and observation time; catalog-derived mappings are labeled separately.

  • Authoritative source; repository metadata signature verified, revision leap-16-0-oss-multiarch:271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c

    Signature verification covers the configured repository metadata chain. It does not certify that the package is safe or suitable.

    Repository-signature verification record
    Signed-object SHA-256
    271b36d440253edf9871ac0c100319fc7443d8f2d54b6b449a72e9414c51577c
    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
    Signed Release → package-index hash linkage

    Path: Not recorded
    Expected SHA-256: Not recorded
    Observed SHA-256: Not recorded
    Result: match verified

perl-JSON-Any Package for openSUSE Leap 16.0 | OpenFactory