Is k-php-serialize safe to use?

k-php-serialize has no known vulnerabilities on the latest version (1.2.1). DepScope rates its health at 42/100 (high risk).

What is the latest version of k-php-serialize?

The latest version of k-php-serialize is 1.2.1, released 2013-06-08.

Does k-php-serialize have known vulnerabilities?

No known vulnerabilities on the latest version of k-php-serialize.

Is k-php-serialize deprecated?

No, k-php-serialize is actively maintained. Latest release: 1.2.1 (2013-06-08).

What are alternatives to k-php-serialize?

Popular alternatives to k-php-serialize in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does k-php-serialize use?

License information for k-php-serialize is not declared in the registry metadata.

k-php-serialize

rubygemsv1.2.1

This module provides two methods: PHP.serialize() and PHP.unserialize(), both of which should be compatible with the similarly named functions in PHP. It can also serialize and unserialize PHP sessions.

2 versions0 deps354,714 weekly dl

keichan34/php-serialize

/ 100

Health

safe to use

[email protected] is safe to use (health: 42/100)

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/k-php-serialize