├── .github
├── ISSUE_TEMPLATE
│ ├── bug_report.md
│ └── feature_request.md
├── pull_request_template.md
├── timer banner.png
└── workflows
│ └── deploy.yml
├── .gitignore
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── README.md
├── SECURITY.md
├── index.html
├── package.json
├── public
├── android
│ ├── android-launchericon-144-144.png
│ ├── android-launchericon-192-192.png
│ ├── android-launchericon-48-48.png
│ ├── android-launchericon-512-512.png
│ ├── android-launchericon-72-72.png
│ └── android-launchericon-96-96.png
├── audio
│ └── countdown voice.mp3
├── img
│ ├── banner.png
│ ├── favicon
│ │ ├── android-chrome-192x192.png
│ │ ├── android-chrome-512x512.png
│ │ ├── apple-touch-icon.png
│ │ ├── favicon-16x16.png
│ │ ├── favicon-32x32.png
│ │ ├── favicon.ico
│ │ └── site.webmanifest
│ └── timer.png
├── ios
│ ├── 100.png
│ ├── 1024.png
│ ├── 114.png
│ ├── 120.png
│ ├── 128.png
│ ├── 144.png
│ ├── 152.png
│ ├── 16.png
│ ├── 167.png
│ ├── 180.png
│ ├── 192.png
│ ├── 20.png
│ ├── 256.png
│ ├── 29.png
│ ├── 32.png
│ ├── 40.png
│ ├── 50.png
│ ├── 512.png
│ ├── 57.png
│ ├── 58.png
│ ├── 60.png
│ ├── 64.png
│ ├── 72.png
│ ├── 76.png
│ ├── 80.png
│ └── 87.png
├── screenShot1.jpg
├── screenShot2.jpg
└── windows11
│ ├── LargeTile.scale-100.png
│ ├── LargeTile.scale-125.png
│ ├── LargeTile.scale-150.png
│ ├── LargeTile.scale-200.png
│ ├── LargeTile.scale-400.png
│ ├── SmallTile.scale-100.png
│ ├── SmallTile.scale-125.png
│ ├── SmallTile.scale-150.png
│ ├── SmallTile.scale-200.png
│ ├── SmallTile.scale-400.png
│ ├── SplashScreen.scale-100.png
│ ├── SplashScreen.scale-125.png
│ ├── SplashScreen.scale-150.png
│ ├── SplashScreen.scale-200.png
│ ├── SplashScreen.scale-400.png
│ ├── Square150x150Logo.scale-100.png
│ ├── Square150x150Logo.scale-125.png
│ ├── Square150x150Logo.scale-150.png
│ ├── Square150x150Logo.scale-200.png
│ ├── Square150x150Logo.scale-400.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-16.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-20.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-24.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-256.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-30.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-32.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-36.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-40.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-44.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-48.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-60.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-64.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-72.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-80.png
│ ├── Square44x44Logo.altform-lightunplated_targetsize-96.png
│ ├── Square44x44Logo.altform-unplated_targetsize-16.png
│ ├── Square44x44Logo.altform-unplated_targetsize-20.png
│ ├── Square44x44Logo.altform-unplated_targetsize-24.png
│ ├── Square44x44Logo.altform-unplated_targetsize-256.png
│ ├── Square44x44Logo.altform-unplated_targetsize-30.png
│ ├── Square44x44Logo.altform-unplated_targetsize-32.png
│ ├── Square44x44Logo.altform-unplated_targetsize-36.png
│ ├── Square44x44Logo.altform-unplated_targetsize-40.png
│ ├── Square44x44Logo.altform-unplated_targetsize-44.png
│ ├── Square44x44Logo.altform-unplated_targetsize-48.png
│ ├── Square44x44Logo.altform-unplated_targetsize-60.png
│ ├── Square44x44Logo.altform-unplated_targetsize-64.png
│ ├── Square44x44Logo.altform-unplated_targetsize-72.png
│ ├── Square44x44Logo.altform-unplated_targetsize-80.png
│ ├── Square44x44Logo.altform-unplated_targetsize-96.png
│ ├── Square44x44Logo.scale-100.png
│ ├── Square44x44Logo.scale-125.png
│ ├── Square44x44Logo.scale-150.png
│ ├── Square44x44Logo.scale-200.png
│ ├── Square44x44Logo.scale-400.png
│ ├── Square44x44Logo.targetsize-16.png
│ ├── Square44x44Logo.targetsize-20.png
│ ├── Square44x44Logo.targetsize-24.png
│ ├── Square44x44Logo.targetsize-256.png
│ ├── Square44x44Logo.targetsize-30.png
│ ├── Square44x44Logo.targetsize-32.png
│ ├── Square44x44Logo.targetsize-36.png
│ ├── Square44x44Logo.targetsize-40.png
│ ├── Square44x44Logo.targetsize-44.png
│ ├── Square44x44Logo.targetsize-48.png
│ ├── Square44x44Logo.targetsize-60.png
│ ├── Square44x44Logo.targetsize-64.png
│ ├── Square44x44Logo.targetsize-72.png
│ ├── Square44x44Logo.targetsize-80.png
│ ├── Square44x44Logo.targetsize-96.png
│ ├── StoreLogo.scale-100.png
│ ├── StoreLogo.scale-125.png
│ ├── StoreLogo.scale-150.png
│ ├── StoreLogo.scale-200.png
│ ├── StoreLogo.scale-400.png
│ ├── Wide310x150Logo.scale-100.png
│ ├── Wide310x150Logo.scale-125.png
│ ├── Wide310x150Logo.scale-150.png
│ ├── Wide310x150Logo.scale-200.png
│ └── Wide310x150Logo.scale-400.png
├── src
├── js
│ └── timer.js
└── scss
│ ├── components
│ ├── _buttons.scss
│ ├── _copyright.scss
│ ├── _cursor.scss
│ ├── _custom_tooltip.scss
│ ├── _header.scss
│ ├── _pulse.scss
│ ├── _scrollbar.scss
│ └── _timer.scss
│ ├── global
│ ├── _colors.scss
│ ├── _fonts.scss
│ └── _reset.scss
│ ├── media
│ ├── _buttons_media.scss
│ ├── _copyright_media.scss
│ ├── _emoji_media.scss
│ ├── _header_media.scss
│ └── _timer_media.scss
│ └── style.scss
├── vite.config.js
└── yarn.lock
/.github/ISSUE_TEMPLATE/bug_report.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Bug report
3 | about: Create a report to help us improve
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Describe the bug**
11 | A clear and concise description of what the bug is.
12 |
13 | **To Reproduce**
14 | Steps to reproduce the behavior:
15 | 1. Go to '...'
16 | 2. Click on '....'
17 | 3. Scroll down to '....'
18 | 4. See error
19 |
20 | **Expected behavior**
21 | A clear and concise description of what you expected to happen.
22 |
23 | **Screenshots**
24 | If applicable, add screenshots to help explain your problem.
25 |
26 | **Desktop (please complete the following information):**
27 | - OS: [e.g. iOS]
28 | - Browser [e.g. chrome, safari]
29 | - Version [e.g. 22]
30 |
31 | **Smartphone (please complete the following information):**
32 | - Device: [e.g. iPhone6]
33 | - OS: [e.g. iOS8.1]
34 | - Browser [e.g. stock browser, safari]
35 | - Version [e.g. 22]
36 |
37 | **Additional context**
38 | Add any other context about the problem here.
39 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature_request.md:
--------------------------------------------------------------------------------
1 | ---
2 | name: Feature request
3 | about: Suggest an idea for this project
4 | title: ''
5 | labels: ''
6 | assignees: ''
7 |
8 | ---
9 |
10 | **Is your feature request related to a problem? Please describe.**
11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12 |
13 | **Describe the solution you'd like**
14 | A clear and concise description of what you want to happen.
15 |
16 | **Describe alternatives you've considered**
17 | A clear and concise description of any alternative solutions or features you've considered.
18 |
19 | **Additional context**
20 | Add any other context or screenshots about the feature request here.
21 |
--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 |
2 | ## Description
3 |
4 |
5 | ## Related Issue
6 |
7 |
8 |
9 |
10 |
11 | ## Motivation and Context
12 |
13 |
14 |
15 |
16 | ## Proposed Changes
17 |
18 |
19 | ### New Feature Submissions:
20 |
21 | 1. [ ] Does your submission pass tests?
22 | 2. [ ] Have you lint your code locally before submission?
23 |
24 | ### Changes to Core Features:
25 |
26 | * [ ] Have you added an explanation of what your changes do and why you'd like us to include them?
27 | * [ ] Have you written new tests for your core changes, as applicable?
28 | * [ ] Have you successfully run tests with your changes locally?
29 |
30 | ## How Has This Been Tested?
31 |
32 |
33 |
34 |
35 | Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
36 |
37 | - [ ] Test A
38 | - [ ] Test B
39 |
40 | **Test Configuration**:
41 | * Firmware version:
42 | * Hardware:
43 | * Toolchain:
44 | * SDK:
45 |
46 | ## Screenshots (if applicable)
47 |
48 |
49 | ## Checklist
50 |
51 |
52 | - [ ] I have performed a self-review of my own code
53 | - [ ] I have commented my code, particularly in hard-to-understand areas
54 | - [ ] I have made corresponding changes to the documentation (if applicable)
55 | - [ ] My changes generate no new warnings or errors
56 | - [ ] I have added tests that prove my fix is effective or that my feature works
57 | - [ ] The code follows the project's coding guidelines and style
58 | - [ ] I have tested the changes locally before pushing them
59 | - [ ] Any dependent changes have been merged and published in downstream modules (if applicable)
60 |
61 | ## Additional Notes
62 |
63 |
64 |
--------------------------------------------------------------------------------
/.github/timer banner.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/Silent-Watcher/timer/b9d6c81547ad76637420a134245f2cfd89105902/.github/timer banner.png
--------------------------------------------------------------------------------
/.github/workflows/deploy.yml:
--------------------------------------------------------------------------------
1 | # Simple workflow for deploying static content to GitHub Pages
2 | name: Deploy static content to Pages
3 |
4 | on:
5 | # Runs on pushes targeting the default branch
6 | push:
7 | branches: ['main']
8 |
9 | # Allows you to run this workflow manually from the Actions tab
10 | workflow_dispatch:
11 |
12 | # Sets the GITHUB_TOKEN permissions to allow deployment to GitHub Pages
13 | permissions:
14 | contents: read
15 | pages: write
16 | id-token: write
17 |
18 | # Allow one concurrent deployment
19 | concurrency:
20 | group: 'pages'
21 | cancel-in-progress: true
22 |
23 | jobs:
24 | # Single deploy job since we're just deploying
25 | deploy:
26 | environment:
27 | name: github-pages
28 | url: ${{ steps.deployment.outputs.page_url }}
29 | runs-on: ubuntu-latest
30 | steps:
31 | - name: Checkout
32 | uses: actions/checkout@v3
33 | - name: Set up Node
34 | uses: actions/setup-node@v3
35 | with:
36 | node-version: 18
37 | cache: 'npm'
38 | - name: Install dependencies
39 | run: npm install
40 | - name: Build
41 | run: npm run build
42 | - name: Setup Pages
43 | uses: actions/configure-pages@v3
44 | - name: Upload artifact
45 | uses: actions/upload-pages-artifact@v1
46 | with:
47 | # Upload dist repository
48 | path: './dist'
49 | - name: Deploy to GitHub Pages
50 | id: deployment
51 | uses: actions/deploy-pages@v1
52 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Created by https://www.toptal.com/developers/gitignore/api/node,visualstudiocode
2 | # Edit at https://www.toptal.com/developers/gitignore?templates=node,visualstudiocode
3 |
4 | ### Node ###
5 | # Logs
6 | logs
7 | *.log
8 | npm-debug.log*
9 | yarn-debug.log*
10 | yarn-error.log*
11 | lerna-debug.log*
12 | .pnpm-debug.log*
13 |
14 | # Diagnostic reports (https://nodejs.org/api/report.html)
15 | report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
16 |
17 | # Runtime data
18 | pids
19 | *.pid
20 | *.seed
21 | *.pid.lock
22 |
23 | # Directory for instrumented libs generated by jscoverage/JSCover
24 | lib-cov
25 |
26 | # Coverage directory used by tools like istanbul
27 | coverage
28 | *.lcov
29 |
30 | # nyc test coverage
31 | .nyc_output
32 |
33 | # Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
34 | .grunt
35 |
36 | # Bower dependency directory (https://bower.io/)
37 | bower_components
38 |
39 | # node-waf configuration
40 | .lock-wscript
41 |
42 | # Compiled binary addons (https://nodejs.org/api/addons.html)
43 | build/Release
44 |
45 | # Dependency directories
46 | node_modules/
47 | jspm_packages/
48 |
49 | # Snowpack dependency directory (https://snowpack.dev/)
50 | web_modules/
51 |
52 | # TypeScript cache
53 | *.tsbuildinfo
54 |
55 | # Optional npm cache directory
56 | .npm
57 |
58 | # Optional eslint cache
59 | .eslintcache
60 |
61 | # Optional stylelint cache
62 | .stylelintcache
63 |
64 | # Microbundle cache
65 | .rpt2_cache/
66 | .rts2_cache_cjs/
67 | .rts2_cache_es/
68 | .rts2_cache_umd/
69 |
70 | # Optional REPL history
71 | .node_repl_history
72 |
73 | # Output of 'npm pack'
74 | *.tgz
75 |
76 | # Yarn Integrity file
77 | .yarn-integrity
78 |
79 | # dotenv environment variable files
80 | .env
81 | .env.development.local
82 | .env.test.local
83 | .env.production.local
84 | .env.local
85 |
86 | # parcel-bundler cache (https://parceljs.org/)
87 | .cache
88 | .parcel-cache
89 |
90 | # Next.js build output
91 | .next
92 | out
93 |
94 | # Nuxt.js build / generate output
95 | .nuxt
96 | dist
97 |
98 | # Gatsby files
99 | .cache/
100 | # Comment in the public line in if your project uses Gatsby and not Next.js
101 | # https://nextjs.org/blog/next-9-1#public-directory-support
102 | # public
103 |
104 | # vuepress build output
105 | .vuepress/dist
106 |
107 | # vuepress v2.x temp and cache directory
108 | .temp
109 |
110 | # Docusaurus cache and generated files
111 | .docusaurus
112 |
113 | # Serverless directories
114 | .serverless/
115 |
116 | # FuseBox cache
117 | .fusebox/
118 |
119 | # DynamoDB Local files
120 | .dynamodb/
121 |
122 | # TernJS port file
123 | .tern-port
124 |
125 | # Stores VSCode versions used for testing VSCode extensions
126 | .vscode-test
127 |
128 | # yarn v2
129 | .yarn/cache
130 | .yarn/unplugged
131 | .yarn/build-state.yml
132 | .yarn/install-state.gz
133 | .pnp.*
134 |
135 | ### Node Patch ###
136 | # Serverless Webpack directories
137 | .webpack/
138 |
139 | # Optional stylelint cache
140 |
141 | # SvelteKit build / generate output
142 | .svelte-kit
143 |
144 | ### VisualStudioCode ###
145 | .vscode/*
146 | .vscode/settings.json
147 | .vscode/tasks.json
148 | !.vscode/launch.json
149 | !.vscode/extensions.json
150 | !.vscode/*.code-snippets
151 |
152 | # Local History for Visual Studio Code
153 | .history/
154 |
155 | # Built Visual Studio Code Extensions
156 | *.vsix
157 |
158 | ### VisualStudioCode Patch ###
159 | # Ignore all local history of files
160 | .history
161 | .ionide
162 |
163 | # Support for Project snippet scope
164 | .vscode/*.code-snippets
165 |
166 | # Ignore code-workspaces
167 | *.code-workspace
168 |
169 | # End of https://www.toptal.com/developers/gitignore/api/node,visualstudiocode
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We as members, contributors, and leaders pledge to make participation in our
6 | community a harassment-free experience for everyone, regardless of age, body
7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
8 | identity and expression, level of experience, education, socio-economic status,
9 | nationality, personal appearance, race, religion, or sexual identity
10 | and orientation.
11 |
12 | We pledge to act and interact in ways that contribute to an open, welcoming,
13 | diverse, inclusive, and healthy community.
14 |
15 | ## Our Standards
16 |
17 | Examples of behavior that contributes to a positive environment for our
18 | community include:
19 |
20 | * Demonstrating empathy and kindness toward other people
21 | * Being respectful of differing opinions, viewpoints, and experiences
22 | * Giving and gracefully accepting constructive feedback
23 | * Accepting responsibility and apologizing to those affected by our mistakes,
24 | and learning from the experience
25 | * Focusing on what is best not just for us as individuals, but for the
26 | overall community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | * The use of sexualized language or imagery, and sexual attention or
31 | advances of any kind
32 | * Trolling, insulting or derogatory comments, and personal or political attacks
33 | * Public or private harassment
34 | * Publishing others' private information, such as a physical or email
35 | address, without their explicit permission
36 | * Other conduct which could reasonably be considered inappropriate in a
37 | professional setting
38 |
39 | ## Enforcement Responsibilities
40 |
41 | Community leaders are responsible for clarifying and enforcing our standards of
42 | acceptable behavior and will take appropriate and fair corrective action in
43 | response to any behavior that they deem inappropriate, threatening, offensive,
44 | or harmful.
45 |
46 | Community leaders have the right and responsibility to remove, edit, or reject
47 | comments, commits, code, wiki edits, issues, and other contributions that are
48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
49 | decisions when appropriate.
50 |
51 | ## Scope
52 |
53 | This Code of Conduct applies within all community spaces, and also applies when
54 | an individual is officially representing the community in public spaces.
55 | Examples of representing our community include using an official e-mail address,
56 | posting via an official social media account, or acting as an appointed
57 | representative at an online or offline event.
58 |
59 | ## Enforcement
60 |
61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
62 | reported to the community leaders responsible for enforcement at
63 | alitabatabaee20@gmail.com.
64 | All complaints will be reviewed and investigated promptly and fairly.
65 |
66 | All community leaders are obligated to respect the privacy and security of the
67 | reporter of any incident.
68 |
69 | ## Enforcement Guidelines
70 |
71 | Community leaders will follow these Community Impact Guidelines in determining
72 | the consequences for any action they deem in violation of this Code of Conduct:
73 |
74 | ### 1. Correction
75 |
76 | **Community Impact**: Use of inappropriate language or other behavior deemed
77 | unprofessional or unwelcome in the community.
78 |
79 | **Consequence**: A private, written warning from community leaders, providing
80 | clarity around the nature of the violation and an explanation of why the
81 | behavior was inappropriate. A public apology may be requested.
82 |
83 | ### 2. Warning
84 |
85 | **Community Impact**: A violation through a single incident or series
86 | of actions.
87 |
88 | **Consequence**: A warning with consequences for continued behavior. No
89 | interaction with the people involved, including unsolicited interaction with
90 | those enforcing the Code of Conduct, for a specified period of time. This
91 | includes avoiding interactions in community spaces as well as external channels
92 | like social media. Violating these terms may lead to a temporary or
93 | permanent ban.
94 |
95 | ### 3. Temporary Ban
96 |
97 | **Community Impact**: A serious violation of community standards, including
98 | sustained inappropriate behavior.
99 |
100 | **Consequence**: A temporary ban from any sort of interaction or public
101 | communication with the community for a specified period of time. No public or
102 | private interaction with the people involved, including unsolicited interaction
103 | with those enforcing the Code of Conduct, is allowed during this period.
104 | Violating these terms may lead to a permanent ban.
105 |
106 | ### 4. Permanent Ban
107 |
108 | **Community Impact**: Demonstrating a pattern of violation of community
109 | standards, including sustained inappropriate behavior, harassment of an
110 | individual, or aggression toward or disparagement of classes of individuals.
111 |
112 | **Consequence**: A permanent ban from any sort of public interaction within
113 | the community.
114 |
115 | ## Attribution
116 |
117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118 | version 2.0, available at
119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120 |
121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
122 | enforcement ladder](https://github.com/mozilla/diversity).
123 |
124 | [homepage]: https://www.contributor-covenant.org
125 |
126 | For answers to common questions about this code of conduct, see the FAQ at
127 | https://www.contributor-covenant.org/faq. Translations are available at
128 | https://www.contributor-covenant.org/translations.
129 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contribution Guidelines
2 |
3 | ### Read the documentation:
4 | Before contributing to the project, make sure to read the documentation thoroughly. This will help you understand the project's goals, structure, and coding conventions.
5 |
6 | ### Fork the project:
7 | Fork the project to your own GitHub account. This will create a copy of the project that you can make changes to without affecting the original project.
8 |
9 | ### Create a new branch:
10 | Create a new branch in your forked project for your changes. This will help keep your changes separate from the original code and make it easier to merge your changes back into the main project.
11 |
12 | ### Write clear and concise code:
13 | Write code that is easy to understand and follow. Use descriptive variable and function names, and comment your code where necessary.
14 |
15 | ### Test your changes:
16 | Before submitting your changes, make sure to test them thoroughly. This will help ensure that your changes work as expected and do not introduce any new bugs.
17 |
18 | ### Follow the project's coding standards:
19 | Make sure to follow the project's coding standards, which are usually listed in the documentation. This includes things like indentation, whitespace, and naming conventions.
20 |
21 | ### Submit a pull request:
22 | When you are ready to contribute your changes back to the main project, submit a pull request. This will allow the project maintainers to review your changes and merge them into the main project if they are deemed appropriate.
23 |
24 | ### 🤗 Be kind and respectful:
25 | Remember that you are contributing to a community project. Be respectful of others' contributions and opinions, and be open to feedback on your own work. Avoid using offensive language or engaging in personal attacks.
26 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2023 Ali t.nazari
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 | 
3 |
4 | # Timer.js 🕰️
5 |
6 | The Timer App is a versatile and intuitive application built with JavaScript that allows you to set and manage timers effortlessly. Whether you need a simple timer for tracking short durations or a countdown for important events, the Timer App has got you covered.
7 |
8 |
9 |
10 |
11 | [](https://github.com/Silent-Watcher/cli-word-guessing-game)
12 |
13 | ## Table of Contents
14 |
15 | - [Features](https://github.com/Silent-Watcher/timer#features)
16 | - [preview](https://github.com/Silent-Watcher/timer#preview)
17 | - [demo](https://github.com/Silent-Watcher/timer#demo)
18 | - [Prerequisites](https://github.com/Silent-Watcher/timer#Prerequisites)
19 | - [Installation](https://github.com/Silent-Watcher/timer#Installation)
20 | - [usage](https://github.com/Silent-Watcher/timer#usage)
21 | - [Acknowledgements](https://github.com/Silent-Watcher/timer#Acknowledgements)
22 | - [Contributing](https://github.com/Silent-Watcher/timer#Contributing)
23 | - [Contact](https://github.com/Silent-Watcher/timer#Contact)
24 | - [License](https://github.com/Silent-Watcher/timer#License)
25 |
26 | ## Features
27 |
28 | - Set timers with a specific duration
29 | - Get notified when the time is up
30 | - Supports both countdowns and regular timers
31 | - Simple and easy-to-use command-line interface
32 | - Cross-platform compatibility
33 |
34 | ## Preview
35 |
36 | Here is a preview of the Timer in action:
37 |
38 | 
39 |
40 | ## Demo
41 |
42 | You can try out the Timer by following this [demo link.](https://silent-watcher.github.io/timer/)
43 |
48 |
49 |
50 | ## Prerequisites
51 |
52 | In order to run this project, you will need to have the following installed on your computer:
53 | - nodejs
54 | - yarn | npm
55 |
56 | ## Installation
57 |
58 | To install the application, follow these steps:
59 |
60 | 1. Clone the repository to your local machine:
61 |
62 |
63 | ```bash
64 | git clone https://github.com/Silent-Watcher/timer
65 | ```
66 |
67 | 2. Navigate to the project directory in your terminal.
68 |
69 |
70 | ```bash
71 | cd timer
72 | ```
73 | 3. Run `yarn` to install the necessary packages.
74 |
75 |
76 | ```bash
77 | yarn
78 | ```
79 |
80 | ## usage
81 |
82 | To start the application, run yarn dev. This will start the application on http://localhost:5173.
83 |
84 | ```bash
85 | yarn dev
86 | ```
87 |
88 | ## Acknowledgements
89 |
90 | - [The build tool and development server.](https://vitejs.dev/)
91 | - [The package manager used in the project.](https://yarnpkg.com/)
92 | - [The animations used in the project.](https://animate.style/)
93 | - [the confetti effect used in the project](https://party.js.org/)
94 |
95 | ## Technologies
96 |
97 |
98 |
99 |
100 |
101 |
102 |
103 |
104 |
105 |
106 | ## Contributing
107 |
108 | Contributions to this project are welcome.
109 | If you encounter any issues or have suggestions for improvement, please open an issue on the GitHub repository.
110 |
111 | Before contributing, please review the contribution guidelines.
112 |
113 | ## Contact
114 |
115 | For additional information or inquiries, you can reach out to the project maintainer:
116 |
117 | - Name: Silent-Watcher
118 | - Email: alitabatabaee20@mail.com
119 |
120 | Feel free to contact the maintainer for any questions or feedback regarding the project.
121 |
122 | ## License
123 |
124 | [MIT](https://choosealicense.com/licenses/mit/)
125 |
126 | This project is licensed under the MIT License. You are free to modify, distribute, and use the code for personal and commercial purposes. See the LICENSE file for details.
127 |
128 |
129 |
130 |
131 |
--------------------------------------------------------------------------------
/SECURITY.md:
--------------------------------------------------------------------------------
1 | # Security Policy
2 | timer.js is committed to ensuring the security and privacy of its users.
3 | This document outlines the security policy for the project, including guidelines, reporting vulnerabilities, and the project's response to security concerns.
4 |
5 | ## Supported Versions
6 |
7 | The following table provides information about the currently supported versions of the battery-tracker project and the associated security updates:
8 |
9 | | Version | Supported |
10 | | ------- | ------------------ |
11 | | 1.0.x | :white_check_mark: |
12 | | 0.1.x | :x: |
13 |
14 |
15 | ## Reporting a Vulnerability
16 |
17 | If you discover any security vulnerabilities or potential risks within the battery-tracker project, please report them immediately to our security team. To report a vulnerability, follow these steps:
18 |
19 | 1. Email us at alitabatabaee20@gmail.com with the subject line "timer.js Security Vulnerability."
20 |
21 | 2. Provide a detailed description of the vulnerability, including the steps to reproduce it, potential impact, and any relevant information.
22 |
23 | 3. If possible, include any proof-of-concept code, logs, or screenshots that demonstrate the vulnerability.
24 |
25 | 4. Our security team will acknowledge your report within 48 hours and work with you to understand and validate the issue.
26 |
27 | 5. We kindly request that you refrain from publicly disclosing the vulnerability until we have had sufficient time to address and remediate the issue.
28 |
29 | ##Security Response
30 | 1. Once a security vulnerability is reported, our security team will review and validate the issue.
31 | 2. We will work diligently to develop a fix or mitigation strategy for the vulnerability.
32 | 3. The fix or mitigation will be implemented in the latest supported version of the project.
33 | 4. A new release containing the security patch will be published as soon as possible.
34 | 5. The security vulnerability will be publicly disclosed, along with the details of the fix, to ensure transparency and awareness among users.
35 |
36 | ## Best Practices
37 | To enhance the security of the CLI Word Guessing Game project, we recommend the following best practices:
38 | - Keep your system and dependencies up to date with the latest security patches.
39 | - Regularly review and audit the project's dependencies for known vulnerabilities.
40 | - Use strong and unique passwords for any associated accounts or services.
41 | - Be cautious when executing third-party scripts or code, as they may pose security risks.
42 | - Verify the integrity of the project's releases by checking digital signatures or hashes when available.
43 |
44 | ## Conclusion
45 | the timer.js project is dedicated to providing a secure and reliable gaming experience.
46 | By following responsible disclosure practices and collaborating with the security community, we strive to promptly address any security concerns. We appreciate the efforts of researchers and users who contribute to the security of the project.
47 |
48 | If you have any further questions or need additional information, please reach out to our security team at alitabatabaee20@gmail.com 😁
49 |
--------------------------------------------------------------------------------
/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 | Timer.js
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |