Merge branch 'main' into 62-storybook-docs-dark-mode

Author: Sunjae95

.github/dependabot.yml

@@ -12,6 +12,12 @@ updates:
         patterns:
           - "storybook"
           - "@storybook/*"
+      react:
+        patterns:
+          - "react"
+          - "react-dom"
+          - "@types/react"
+          - "@types/react-dom"
 
   - package-ecosystem: "github-actions"
     pull-request-branch-name:

CODE_OF_CONDUCT.md

@@ -0,0 +1,127 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,5 @@
+# 기여 가이드
+
+DaleUI에 기여하고 싶으신가요? 여러분의 기여를 환영합니다!
+
+자세한 기여 가이드는 [위키 기여 페이지](https://github.com/DaleStudy/daleui/wiki/Contributing)를 참고해주세요.

SECURITY.md

@@ -0,0 +1,43 @@
+# 보안 정책
+
+안전하게 취약점을 신고해 주셔서 감사합니다. 이 문서는 보안 취약점을 신고하는 방법과 처리 방식에 대해 설명합니다.
+
+## 취약점 신고
+
+프로젝트의 보안 취약점을 발견하셨다면, 다음 단계를 따라 신고해 주시기 바랍니다.
+
+1. **신고 방법:**
+
+   - 깃허브 이슈: [https://github.com/dale-study/daleui/issues](https://github.com/dale-study/daleui/issues)
+   - 보안 관련 이슈는 'security' 라벨을 사용해주세요.
+
+2. **신고 내용에 포함할 사항:**
+
+   - 취약점 설명 및 재현 단계
+   - 예상되는 영향도와 위협 수준
+   - 관련 로그, 스크린샷, 코드 스니펫 등 추가 자료 (가능한 경우)
+
+3. **기밀 유지:**
+
+   - 제출된 정보는 기밀로 취급되며, 조사 완료 후 결과를 공유해 드릴 예정입니다.
+   - 공격 벡터나 재현 방법과 같은 민감한 정보는 일반에 공개하지 않습니다.
+
+## 처리 절차
+
+1. **접수 확인:**
+
+   - 취약점 신고를 받은 후 가능한 빠른 시간 내에 깃허브을 통해 접수 확인 답변을 드리겠습니다.
+
+2. **조사 및 대응:**
+
+   - 보고된 취약점을 검토하고, 커뮤니티 멤버들과 함께 대응 계획을 수립합니다.
+   - 신고자가 요청하는 경우 조사 진행 상황을 공유해 드립니다.
+
+3. **결과 공유:**
+
+   - 취약점 패치가 완료되면, 해당 사항을 깃허브 릴리스 노트에 공개합니다.
+   - 완료 후 신고자님께 이슈를 통해 처리 결과를 알려드립니다.
+
+## 추가 정보
+
+보안 문제에 대한 자세한 문의나 건의 사항은 [깃허브 이슈](https://github.com/dale-study/daleui/issues)를 통해 연락해 주시기 바랍니다.