Repository navigation
Description
Community Readiness Self-Check (optional, for your own reflection)
- My project has at least one merged pull request from someone other than me or an automated bot.
- My project has been public for at least 3 months.
- My project has organic GitHub stars, forks, or package downloads that I can't attribute to my own testing or CI activity.
- I already have a presence in the .NET Foundation Discord and/or other .NET community spaces.
Project Name
Nullabe.Extended
License
MIT
Contributor
Tom Englert (tom-englert)
Existing OSS Project?
Yes
Source Code URL
https://github.com/tom-englert/Nullable.Extended
Project Homepage URL
No response
Project Transfer Signatories
Thomas Englert (mail@tom-englert.de)
Description
Roslyn analyzer, Visual Studio extension and MCP server to find, justify and remove null-forgiving operators (!) in C# code.
What are you hoping from the foundation
Visibility and credibility in the .NET community, a neutral home that outlives a single maintainer, access to foundation infrastructure and benefits (code signing), and a path to attract additional maintainers and contributors.
Name
Tom Englert
GitHub Profile URL
https://github.com/tom-englert
Committers
tom-englert (maintainer; independent)
Discord Ids
tom-englert (tomenglert)
Governance Model
The project is maintained by its lead maintainer. Changes are proposed via GitHub pull requests, built and tested by GitHub Actions CI, and reviewed and merged by the maintainer. Decisions are made by the maintainer, with discussion in GitHub issues. New committers are invited by the maintainer after a track record of quality contributions.
CLA
- If already an OSS project, was a Contribution License Agreement in place for contributions accepted?
How does the project check who has signed one?
No response
CLA Notification Alias
Select the Project Transfer Agreement model
Contribution
Repository Layout
move to dotnet/Nullable.Extended if applicable.
Eligibility Criteria
- The project is built on the .NET platform and/or creates value within the .NET ecosystem.
- The project produces source code for distribution to the public at no charge.
- The project's code is easily discoverable and publicly accessible (preferably on GitHub).
- The project contains a build script that can produce deployable artifacts that are identical to the official deployable artifacts, with the exception of code signing (Exception may be granted for strong name keys, though strongly encouraged to be committed. Exception relies on OSS signing being in the build script for public builds).
- When applicable, project must use reproducible build settings in its toolchain.
- The project uses Source Link.
- The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).
- The project code signs their artifacts as appropriate.
- The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.
- Libraries that are mandatory dependencies of the project are offered under a standard, permissive open source license which has been approved by the .NET Foundation (exceptions include a dependency that is required by the target platform where no alternative open source dependency is available such as the .NET Framework or a hardware specific library).
- Committers are bound by a Contributor License Agreement (CLA) and/or are willing to embrace the .NET Foundation's CLA when the project becomes a Member.
- The copyright ownership of everything that the project produces is clearly defined and documented.
- The project has a public issue tracker where the status of any defect can be easily obtained.
- The project has a published Security Policy.
- The project has a home page which provides high level information about its status and purpose.
- The project has a public communication channel where community members can engage with maintainers.
- The project has a publicly available location where members can review and contribute to documentation.
Describe why you are applying for Project Membership.
Nullable.Extended is widely used (2.1M NuGet downloads, many OS projects on GH use it) but maintained by essentially one person. Joining the foundation would give the project a sustainable home, more visibility in the .NET community, and shared infrastructure and governance practices.
Infrastructure Requirements Summary
- Builds run on GitHub Actions: No build server required.
- The analyzer ships to NuGet, and the VSIX to the VS Marketplace and the Open VSIX Gallery: No hosting required.
- Authenticode code signing for the VSIX and packages via the foundation's signing service: Required
Additional Notes
- Similar projects: there are none I'm aware of that specifically audit null-forgiving operators with justifications.
- Scope: the MCP server and agent skill are a recent addition.
- Early help wanted: more maintainers and a second reviewer.
Activity
[-]Issue: New .NET Foundation Project Application - Nullabe.Extended[/-][+]New .NET Foundation Project Application - Nullabe.Extended[/+]