Is sexp_processor safe to use?

sexp_processor has no known vulnerabilities on the latest version (4.17.5). DepScope rates its health at 63/100 (moderate risk).

What is the latest version of sexp_processor?

The latest version of sexp_processor is 4.17.5, released 2025-12-24.

Does sexp_processor have known vulnerabilities?

No known vulnerabilities on the latest version of sexp_processor.

Is sexp_processor deprecated?

No, sexp_processor is actively maintained. Latest release: 4.17.5 (2025-12-24).

What are alternatives to sexp_processor?

Popular alternatives to sexp_processor in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does sexp_processor use?

sexp_processor is licensed under MIT.

sexp_processor

rubygemsv4.17.5

sexp_processor branches from ParseTree bringing all the generic sexp processing tools with it. Sexp, SexpProcessor, Environment, etc... all for your language processing pleasure.

License MITpermissive20 versions0 deps917,908 weekly dl

seattlerb/sexp_processor

/ 100

Health

safe to use

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

Health breakdown0 – 100

15/25

maintenance

14/20

popularity

25/25

security

9/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/sexp_processor