Trending repositories

Ranked by Attention Score: stars gained over the last 180 complete days

Period

Sort order

Tags: Mocking

1.ChangemakerStudios / Papercut-SMTP

Papercut SMTP -- The Simple Desktop Email Server

papercut
smtp-server
smtp
testing
server
wpf
+3 more

C#APACHE-2.03.3K total305 forks

+70 stars

from 3,267 · score 4.26

2.devlooped / moq

The most popular and friendly mocking framework for .NET

C#MIT6.4K total831 forks

+68 stars

from 6,346 · score 4.23

3.nsubstitute / NSubstitute

A friendly substitute for .NET mocking libraries.

c-sharp
dotnet
dot-net
testing
testing-tools
test
+6 more

C#Other license3K total281 forks

+46 stars

from 2,937 · score 3.85

4.FakeItEasy / FakeItEasy

The easy mocking library for .NET

mocking
fake-objects
dotnet
dotnet-core
hacktoberfest

C#MIT1.9K total181 forks

+33 stars

from 1,821 · score 3.53

5.harrison314 / BouncyHsm

Bouncy Hsm is a software simulator of HSM and smartcard simulator with HTML UI, REST API and PKCS#11 interface.

blazor
blazor-webassembly
bouncycastle
cryptography
csharp
hsm
+2 more

C#BSD-3-CLAUSE205 total29 forks

+29 stars

from 176 · score 3.40

6.richardszalay / mockhttp

Testing layer for Microsoft's HttpClient library. Create canned responses using a fluent API.

dotnet
httpclient
testing
mocking
dotnetcore

C#MIT1.8K total90 forks

+13 stars

from 1,751 · score 2.64

7.ttu / dotnet-fake-json-server

Fake JSON Server is a Fake REST API that can be used as a Back End for prototyping or as a template for a CRUD Back End.

csharp
webapi
dotnet-core
dynamic
json
fake-data
+3 more

C#MIT409 total94 forks

+7 stars

from 402 · score 2.08

8.natenho / Mockaco

🐵 HTTP mock server, useful to stub services and simulate dynamic API responses, leveraging ASP.NET Core features, built-in fake data generation and pure C# scripting

csharp
mock-server
roslyn
faker
mocks-generator
aspnet
+11 more

C#Other license351 total40 forks

+4 stars

from 347 · score 1.61

9.justeattakeaway / httpclient-interception

A .NET library for intercepting server-side HTTP requests

httpclient
netstandard
dotnet
dotnet-core
c-sharp

C#APACHE-2.0386 total32 forks

+2 stars

from 384 · score 1.10

Order: Attention Score

Most net stars gained in the window first. The score only puts this gain on a log scale, so the order is the order of the gain.

How the ranking works

Ranked by stars gained in the window. The score is the natural log of one plus that gain, so a repository's rank is exactly its star gain's rank.

score = log1p(net stars gained in the trailing T complete UTC days)

A repository is ranked only when its Star History covers every day of the window and its latest Observation is not missing.

The longest window is 180 days. Star History from the Repository Host goes back at most 180 days before the first daily record that AwesomeRepos made for the repository. A longer window needs more of these daily records first. A repository younger than the window does not rank in it.

The filters select from the same eligible repositories. A repository matches the topics when it has any of them. Total stars is the count now. Last push and creation on the Repository Host count back from the start of today (UTC). The counts beside the languages, licenses, and topics include all ranked repositories in the window. A Tag holds the repositories that have it. See Tags.

A new repository enters the index when it gains stars faster than the published admission threshold, whatever its size. A repository stays in the index after it enters. Thus an archived repository can still rank.

Browse the Repository Index