Is DotNetOpenAuth.OpenId.RelyingParty safe to use?

DotNetOpenAuth.OpenId.RelyingParty has no known vulnerabilities on the latest version (5.0.0-alpha3). DepScope rates its health at 49/100 (high risk).

What is the latest version of DotNetOpenAuth.OpenId.RelyingParty?

The latest version of DotNetOpenAuth.OpenId.RelyingParty is 5.0.0-alpha3, released 2013-10-23.

Does DotNetOpenAuth.OpenId.RelyingParty have known vulnerabilities?

No known vulnerabilities on the latest version of DotNetOpenAuth.OpenId.RelyingParty.

Is DotNetOpenAuth.OpenId.RelyingParty deprecated?

No, DotNetOpenAuth.OpenId.RelyingParty is actively maintained. Latest release: 5.0.0-alpha3 (2013-10-23).

What are alternatives to DotNetOpenAuth.OpenId.RelyingParty?

DepScope has no curated alternatives for DotNetOpenAuth.OpenId.RelyingParty at this time.

What license does DotNetOpenAuth.OpenId.RelyingParty use?

License information for DotNetOpenAuth.OpenId.RelyingParty is not declared in the registry metadata.

DotNetOpenAuth.OpenId.RelyingParty

nugetv5.0.0-alpha3

Increase conversion rates to your web site by lowering the bar to create an account with your site, by allowing customers to use accounts they already have with other sites, such as Google and Yahoo!

24 versions1 maintainers1 deps90,114 weekly dl

http://www.dotnetopenauth.net/

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

DotNetOpenAuth.OpenId.Core

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/nuget/DotNetOpenAuth.OpenId.RelyingParty

Last updated · 2013-10-23T04:01:30.297+00:00