Add best practices on key management & not getting hacked
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by locating the Development Best Practices section in this documentation repository and review its existing structure and guidance. Add developer-focused recommendations covering malicious dependencies and avoiding accidental commits of real keys, with the section complete and consistent with surrounding documentation.
Written by the indexing model from the issue text.
Description
We should add this to Development Best Practices section specifically geared towards developers (avoiding malicious dependencies, accidentally committing your real keys, etc.
- Dominant language
- No language data
- Stars
- 17
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
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.
More from dOrgTech/docs
-
Handbook
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Handbook
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Handbook
Difficulty 5/5 Over a week Newbie friendliness 15/100
Similar issues
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
feature pydanty:is-working
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pydantic/pydantic-ai#8647 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100