[DOCS] generating-provenance-statements
Open
Nobody has claimed this yet.
content
- Dominant language
- MDX
- Stars
- 711
- Forks
- 4.2k
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 3
Description
Is there an existing issue for this?
- I have searched the existing issues
This is a CLI Docs Problem, not another kind of Docs Problem.
- This is a CLI Docs Problem.
Description of Problem
I see documentation of how to use npm publish provenance, but am missing instructions of how registries (non github) can support the NPM provenance capability. does such a documentation exist?
Potential Solution
No response
Affected URL
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
Start at the affected URL and review its existing provenance-statement guidance, then trace any referenced registry or provenance documentation. Clarify whether and how non-GitHub registries can support npm provenance; done means adding verified instructions or an authoritative link, with scope and limitations stated.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100