TM security topics for docs
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 11
- Forks
- 22
- Avg merge
- 7d 3h
- Merged PRs (30d)
- 2
Description
https://github.tools.sap/cx-commerce/spasec/issues?q=is%3Aopen+is%3Aissue+label%3Atype%2Fdoc
4 issues as of Sept17
One question - do these tickets have an expiration date?
Like if we do fixes in the future, we remove these mentions?
- https://github.tools.sap/cx-commerce/spasec/issues/13
Input validation - XML - https://github.tools.sap/cx-commerce/spasec/issues/11
Clickjacking - https://github.tools.sap/cx-commerce/spasec/issues/4
Authentication - HTTPS - https://github.tools.sap/cx-commerce/spasec/issues/2
Session Management
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
Review the linked spasec issues 13, 11, 4, and 2 and compare their topics with the documentation. Clarify whether these security mentions should remain after future fixes and document the agreed expiration or removal rule.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100