microsoft / microsoft/RulesEngine

Is there any plan to provide Microsoft-backed digital signatures for RulesEngine DLLs and dependencies?

Open
#747 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
4.4k
Forks
616
Avg merge
6m
Merged PRs (30d)
2

Description

Hello RulesEngine team,

We are evaluating RulesEngine for use in our future software development projects. Our company extensively uses Microsoft products and technologies, and one of our internal security and software governance requirements is that third-party DLLs used in our products must have a trusted digital signature.

While reviewing the official NuGet package:

https://www.nuget.org/packages/RulesEngine

and the GitHub repository:

https://github.com/microsoft/RulesEngine

we noticed that the generated DLLs do not appear to include a Microsoft digital signature, even though the project is hosted under the official Microsoft GitHub organization.

The DLLs we checked include:

RulesEngine.dll
FastExpressionCompiler.dll
FluentValidation.dll
System.Linq.Dynamic.Core.dll
We also noticed that some dependencies are not owned by Microsoft:

https://www.nuget.org/packages/FastExpressionCompiler/
https://www.nuget.org/packages/FluentValidation/
https://www.nuget.org/packages/System.Linq.Dynamic.Core/
Our question is:

Is there any plan to provide Microsoft digital signatures, or any official Microsoft-backed signature/certificate, for the DLLs produced by this project or for Microsoft-hosted/supported open-source projects such as RulesEngine?

Alternatively, is there any official guidance from the team on how organizations with strict DLL-signing requirements should consume this package and its dependencies?

This clarification would help us determine whether RulesEngine can be adopted in environments with strict security, compliance, and software supply-chain policies.

Thank you for your support and for maintaining this project.

Kind regards,
Ali Rasoulian

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reviewing the RulesEngine NuGet package and the listed DLLs, then determine how package signing and dependency ownership are handled. Done would require an official team decision on Microsoft-backed signatures or documented guidance for organizations with strict signing requirements.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
release, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.