microsoft / microsoft/AdaptiveCards
Produce compliant artifacts
Open
Nobody has claimed this yet.
Epic
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Packages should not contain any vulnerable dependencies at time of release, and all released artifacts should satisfy any Microsoft signing requirements.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by determining which released artifacts and dependencies are in scope, then identify the applicable Microsoft signing requirements. Done means release artifacts contain no vulnerable dependencies and satisfy the required signing checks.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100