Is Microsoft.Bcl safe to use?

Microsoft.Bcl has no known vulnerabilities on the latest version (1.1.10). DepScope rates its health at 20/100 (critical risk).

What is the latest version of Microsoft.Bcl?

The latest version of Microsoft.Bcl is 1.1.10, released 2015-02-25.

Does Microsoft.Bcl have known vulnerabilities?

No known vulnerabilities on the latest version of Microsoft.Bcl.

Is Microsoft.Bcl deprecated?

Yes, Microsoft.Bcl is deprecated: This package has been deprecated as part of the .NET Package Deprecation effort. You can learn more about it from https://github.com/dotnet/announcements/issues/217

What are alternatives to Microsoft.Bcl?

DepScope has no curated alternatives for Microsoft.Bcl at this time.

What license does Microsoft.Bcl use?

License information for Microsoft.Bcl is not declared in the registry metadata.

Microsoft.Bcl

nugetv1.1.10deprecated

This packages enables projects targeting down-level platforms to use some of the types added in later versions including: - CallerMemberNameAttribute - CallerLineNumberAttribute - CallerFilePathAttribute - Tuple<T1, T2, ...> - IProgress<T> - IStructuralComparable - IStructuralEquatable - Task - InvalidDataException These types are "unified" to their later version equivalent. For example, when running on .NET Framework 4.5, IProgress<T> from this package will be seen by the runtime as the same

11 versions1 maintainers1 deps540,281 weekly dl

http://go.microsoft.com/fwlink/?LinkID=280057

/ 100

Health

find alternative

Microsoft.Bcl is deprecated — find an alternative

Low health score (20/100)
Package is deprecated

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

Microsoft.Bcl.Build

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/nuget/Microsoft.Bcl

Last updated · 2015-02-25T01:21:24.653+00:00