Is sphinxext.remoteliteralinclude safe to use?

sphinxext.remoteliteralinclude has no known vulnerabilities on the latest version (0.6.1). DepScope rates its health at 59/100 (high risk).

What is the latest version of sphinxext.remoteliteralinclude?

The latest version of sphinxext.remoteliteralinclude is 0.6.1, released 2026-03-29.

Does sphinxext.remoteliteralinclude have known vulnerabilities?

No known vulnerabilities on the latest version of sphinxext.remoteliteralinclude.

Is sphinxext.remoteliteralinclude deprecated?

No, sphinxext.remoteliteralinclude is actively maintained. Latest release: 0.6.1 (2026-03-29).

What are alternatives to sphinxext.remoteliteralinclude?

Popular alternatives to sphinxext.remoteliteralinclude in PyPI include: boto3, packaging, idna, certifi, urllib3.

What license does sphinxext.remoteliteralinclude use?

sphinxext.remoteliteralinclude is licensed under MIT.

sphinxext.remoteliteralinclude

pypiv0.6.1

Extending literalinclude to include remote URLs

License MITpermissive7 versions1 maintainers2 deps5,627 weekly dl

wpilibsuite/sphinxext-remoteliteralinclude

/ 100

Health

use with caution

[email protected] low health (59/100) — consider alternatives

Moderate health score (59/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

6/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

sphinx six

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/sphinxext.remoteliteralinclude