Bernt
58ca4e68db
- Go backend API with full CRUD for all modules (CRM, Sales, Finance, HR, Legal, Marketing, Support, Purchase, Inventory, Projects, Automation, Analytics) - Rust analytics service with parallel report generation - C runtime with POSIX shared memory IPC - PostgreSQL schema with 30+ tables, full migrations - Redis cache, sessions, pub/sub - Kafka event streaming with Zookeeper - WebSocket hub for real-time updates - Automation engine with cron jobs, workflows, event triggers - JWT authentication, multi-tenant from start - Docker Compose with all services - Nginx reverse proxy with rate limiting - Integration tests passing - Feature gap analysis against Fortnox/Odoo/Visma Refs: BOC-001
25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
# Security Policies and Procedures
|
|
|
|
## Reporting a Bug
|
|
|
|
The `send` team and community take all security bugs seriously. Thank you
|
|
for improving the security of Express. We appreciate your efforts and
|
|
responsible disclosure and will make every effort to acknowledge your
|
|
contributions.
|
|
|
|
Report security bugs by emailing the current owner(s) of `send`. This information
|
|
can be found in the npm registry using the command `npm owner ls send`.
|
|
If unsure or unable to get the information from the above, open an issue
|
|
in the [project issue tracker](https://github.com/pillarjs/send/issues)
|
|
asking for the current contact information.
|
|
|
|
To ensure the timely response to your report, please ensure that the entirety
|
|
of the report is contained within the email body and not solely behind a web
|
|
link or an attachment.
|
|
|
|
At least one owner will acknowledge your email within 48 hours, and will send a
|
|
more detailed response within 48 hours indicating the next steps in handling
|
|
your report. After the initial reply to your report, the owners will
|
|
endeavor to keep you informed of the progress towards a fix and full
|
|
announcement, and may ask for additional information or guidance.
|