e30ae8ed09
- App.tsx: full navigation (Auth stack + Main tabs with 5 screens) - Auth: LoginScreen, RegisterScreen, ForgotPasswordScreen - HomeScreen: dashboard with IoT metrics, weather widget, alerts, quick actions, sensors - MapScreen: interactive map with layer toggles (6 layers) - MarketplaceScreen: categories (6), products (5), search - ChatScreen: AI chat with quick prompts (4), bot responses - ProfileScreen: user info, stats, menu (9 items), logout - AlertsScreen: alert list with severity, acknowledge - SensorsScreen: sensor list with type filters (6 types), search - ZonesScreen: zone cards with stats - SettingsScreen: language picker (FR/EN/ES/DE), privacy, about - Stores: iotStore (sensors, zones, alerts), notificationStore, uiStore + i18n - Hooks: useSensors, useAlerts, useNotifications, useLocation - Components: Card, Button, LoadingSpinner, ErrorBoundary, Header - Services: iotService, notificationService (with axios API client) - Utils: formatters (temp, AQI, noise, dates), validators (email, password, IBAN) - Theme: colors.ts with full design system (Blue Ocean palette) - Ditto: fixed MongoDB connection, new JWT secrets, official gateway image
44 lines
1.7 KiB
Markdown
44 lines
1.7 KiB
Markdown
# Security Policies and Procedures
|
|
|
|
This document outlines security procedures and general policies for the Connect
|
|
project.
|
|
|
|
* [Reporting a Bug](#reporting-a-bug)
|
|
* [Disclosure Policy](#disclosure-policy)
|
|
* [Comments on this Policy](#comments-on-this-policy)
|
|
|
|
## Reporting a Bug
|
|
|
|
The Connect team and community take all security bugs in Connect seriously.
|
|
Thank you for improving the security of Connect. We appreciate your efforts and
|
|
responsible disclosure and will make every effort to acknowledge your
|
|
contributions.
|
|
|
|
Report security bugs by emailing the lead maintainer in the README.md file.
|
|
|
|
The lead maintainer 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 security team will
|
|
endeavor to keep you informed of the progress towards a fix and full
|
|
announcement, and may ask for additional information or guidance.
|
|
|
|
Report security bugs in third-party modules to the person or team maintaining
|
|
the module. You can also report a vulnerability through the
|
|
[Node Security Project](https://nodesecurity.io/report).
|
|
|
|
## Disclosure Policy
|
|
|
|
When the security team receives a security bug report, they will assign it to a
|
|
primary handler. This person will coordinate the fix and release process,
|
|
involving the following steps:
|
|
|
|
* Confirm the problem and determine the affected versions.
|
|
* Audit code to find any potential similar problems.
|
|
* Prepare fixes for all releases still under maintenance. These fixes will be
|
|
released as fast as possible to npm.
|
|
|
|
## Comments on this Policy
|
|
|
|
If you have suggestions on how this process could be improved please submit a
|
|
pull request.
|