</>PackageGraphPackageGraph

BenchmarkDotNet

NuGetv0.15.8

Powerful .NET library for benchmarking

Adopt with care

BenchmarkDotNet is usable, with caveats. Pulls in 108 transitive packages (at least — some of the tree is still being crawled).

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • BMaintenance: grade B, Good.

    Last published 284 days ago. 9 releases in the last 2 years.

  • DWeight: grade D, Poor — a real concern.

    Pulls in 108 transitive packages (at least — some of the tree is still being crawled).

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding BenchmarkDotNet to a project.

15
Direct dependencies

Runtime packages this one declares itself.

108
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

6
Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Licenses in the dependency tree

MIT

Every license you inherit by installing BenchmarkDotNet, not just its own. Check this before a legal review, not after.

Compatibility

.NET
No constraint declared

BenchmarkDotNet vs the alternatives

Packages solving a similar problem in the nuget ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
BenchmarkDotNetthis page00MIT9 months ago
BenchmarkDotNet.Annotations01MIT1 day ago
Perfolizer01MIT1 day ago

Dependencies

Declared by BenchmarkDotNet v0.15.8. Runtime dependencies are installed with the package; dev dependencies are not.

Relationship graph

Dependencies (left) and dependents (right) of BenchmarkDotNet.

Release history

9 releases in the last two years, typically about 30 days apart.

Recent versions of BenchmarkDotNet
VersionPublishedLicense
0.16.0-preview.12 months agoMIT
0.15.8latest9 months agoMIT
0.15.610 months agoMIT
0.15.510 months agoMIT
0.15.411 months agoMIT
0.15.311 months agoMIT
0.15.21 year agoMIT
0.15.11 year agoMIT
0.15.01 year agoMIT
0.14.02 years agoMIT
0.13.122 years agoMIT
0.13.112 years agoMIT
0.13.102 years agoMIT
0.13.92 years agoMIT
0.13.83 years agoMIT

Overview

BenchmarkDotNet is an NuGet package that powerful .NET library for benchmarking. The latest version is 0.15.8, released under the MIT license.

Who should use it

Teams working in the NuGet ecosystem who need powerful .NET library for benchmarking and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your NuGet stack.

Pros

  • Clear open-source license (MIT).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Frequently asked questions

Should I use BenchmarkDotNet?

BenchmarkDotNet is usable, with caveats. Pulls in 108 transitive packages (at least — some of the tree is still being crawled).

How do I install BenchmarkDotNet?

Run `dotnet add package BenchmarkDotNet` to add BenchmarkDotNet to your NuGet project.

How many dependencies does BenchmarkDotNet have?

BenchmarkDotNet declares 15 direct dependencies and pulls in 108 packages in total once its runtime tree is resolved.

What license is BenchmarkDotNet released under?

BenchmarkDotNet is distributed under the MIT license.

Is BenchmarkDotNet still maintained?

The most recent release of BenchmarkDotNet (v0.15.8) was published 9 months ago.