You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cf9770d
Browse filesBrowse the repository at this point in the historyBrowse files
We strictly use `npm ci` to ensure reproducible builds.
15
+
```bash
16
+
npm ci
17
+
```
18
+
19
+
3.**Start the development server:**
20
+
```bash
21
+
npm run dev
22
+
```
23
+
24
+
## Development Guidelines
25
+
-**Pull Requests Required**: Never push new features directly to the `main` branch. Always create a new branch and push your changes as a Pull Request (PR) for review.
26
+
-**Pre-PR Checks**: Run `npm run lint` and `npm run test` before opening any PR — don't open a PR with failing checks.
27
+
-**Performance Reporting**: Performance changes require a before/after bundle size comparison in the PR description (just paste the Vite build output).
Currently, only the latest version of PaperCache receives security updates. Please ensure you are running the most recent version available.
6
+
7
+
## Reporting a Vulnerability
8
+
9
+
We take the security of PaperCache seriously. If you discover a security vulnerability, we would appreciate it if you could report it privately so it can be addressed before being disclosed publicly.
10
+
11
+
Please report any security issues to: **adityasharma.variable@gmail.com**
12
+
13
+
When reporting, please include:
14
+
- A description of the vulnerability.
15
+
- Steps to reproduce the issue.
16
+
- Any potential impact you have identified.
17
+
18
+
You should receive an acknowledgment of your report within 48 hours, along with an estimated timeline for a fix. Thank you for helping keep PaperCache secure!
0 commit comments