Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jwt-sd-dotnet 2024 Annual Review #202

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions docs/projects/reviews/2024/2024-sd-jwt-dotnet-annual.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
# 2024 sd-jwt-dotnet (SD-JWT Implementation)

## Project Health

The main focus of this project was to provide a .Net implementation for the
IETF SD-JWT draft. As such, the code has reflected the developments in the
specification over the last year and is up to date with the latest version of
the draft.

## Maintainer Diversity

As before, the project is maintained by a single maintainer.
It's expected to have a single maintainer for the next year as well.

## Project Adoption

The primary objective of the project is to deliver a reference implementation for the SD-JWT draft.
This project is intended solely for experimental purposes.

## Goals

### Performance Against Prior Goals

The project successfully achieved its initial goal, but it was not widely adopted, and the original program was only partially completed

### Next Year's Goals

As before, the main goal of the project is to provide a reference implementation
for the SD-JWT draft. The project will continue to track the development of the
draft, including a potential transition to an RFC. The project will also continue
to exist as a reference for SD-JWT implementations.

## Help Required

The project is maintainable with one maintainer and no further aid is needed.
We are planning to automate the process (maybe using github actions).

## Project Lifecycle Stage Recommendation

The project is recommended to remain in the Labs stage.