Nimblesite / Nimblesite/SharpLsp
Sign + notarize the macOS binaries
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 132
- Forks
- 5
- Avg merge
- 6h 24m
- Merged PRs (30d)
- 27
Description
TODO: Developer ID sign (codesign --options runtime --timestamp) + notarize (xcrun notarytool submit --wait) + staple each macOS binary, then keep cosign provenance in addition.
Binaries to sign:
sharplsp-lsp(Rust)- C# .NET sidecar
- F# .NET sidecar
macOS signing is a solved process — this is working through each binary. See https://github.com/Nimblesite/Shipwright ([SWR-SIGN-APPLE-WORKFLOW]).
Contributor guide
No contributing guide indexed for this repository
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
Start by reading the Shipwright [SWR-SIGN-APPLE-WORKFLOW] reference, then locate SharpLsp's macOS binary build and release entry points for sharplsp-lsp and both .NET sidecars. Verify Developer ID signing, notarytool submission, stapling, and retained cosign provenance for each binary; done means all three are signed, notarized, stapled, and still have provenance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, fsharp, macos, rust
- Domain
- devops, release, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100