memorio 4.5.3 → 4.6.4

package/markdown/CHANGELOG.md

@@ -4,6 +4,77 @@ All notable changes to this project will be documented in this file.
 
 ---
 
+## v4.6.1 (Security Patch) - 2026-08-14 — CRITICAL Security Fix
+
+### 🔐 Security NOTICE (v4.6.0)
+
+**CRITICAL**: A Gitea Personal Access Token was accidentally committed to `.npmrc` in v4.6.0
+
+**Affected**: `v4.6.0` tag and all builds from that version
+
+**Action Required**:
+- **IMMEDIATE**: Revoke ALL tokens on Gitea Packages by admin access
+- **GENERATE**: Create new PAT with scope `write:package` only
+- **CONFIGURE**: Add as secret `PAT` in GitHub Actions or Gitea Actions
+- **UPGRADE**: Use v4.6.1 where the token is replaced with `${PAT}` environment variable
+
+The hardcoded token `2f398d5d7a734781e96108fdd0dbbabad41ef77a` has been removed in v4.6.1.
+
+### 🐛 Bug Fixes
+
+- **SECURITY**: Removed hardcoded Gitea PAT from `.npmrc` (exposed token remediated)
+- Replaced with environment variable `${PAT}` for secure authentication
+
+### 📝 Documentation Updates
+
+- `.npmrc`: Token replaced with environment variable reference
+- `.gitea/workflows/npm.yml`: Configured to use secrets `GITEA_USER` and `PAT`
+
+---
+
+## v4.6.0 (Previous - SECURITY ISSUE) - 2026-08-13 — Refactoring & Documentation
+
+**⚠️ WARNING**: This version had a hardcoded PAT token that was later remediated in v4.6.1**
+
+### 🐛 Bug Fixes
+
+- Fixed circular import in `idb/index.ts` → `core/global`
+- Fixed dead `globalThis._propertyAccessLog` reference in `observer`
+- Fixed `dispatch.remove(f)` tuple bug in `functions/dispatch.ts`
+- Fixed `logger.isDebugEnabled` using wrong module reference
+- Removed dead `propertyAccessLog` / `pushPropertyAccess` from `core/internal.ts`
+- Removed duplicate path-tracking block in `state` get handler
+- Removed redundant `?? key` fallback in `state` set handler
+
+### 🔧 Code Refactoring
+
+- **Self-contained modules**: All modules now work independently without internal `globalThis.memorio.*` reads/writes
+- **Module-local state**: Created `core/internal.ts` for module-local singletons
+- **Bootstrap-only global**: `core/global.ts` now only publishes to `globalThis.memorio` at initialization
+- **Removed dead code**: `core/constructor.ts` deleted (unused)
+- **Extracted helpers**: `_read`/`_write`/`_remove` in `store` and `session` to eliminate duplication
+- **Fixed circular imports**: `dispatch` → `observer` via `globalThis.events`
+
+### 📝 Documentation Updates
+
+- `docs/README.md`: Added Classic `import { state } from 'memorio'` section, improved badges layout, enhanced "Why memorio?" comparison table
+- `docs/markdown/STORE.md`: Added classic import note
+- `docs/markdown/IMPORT.md`: New file for named export guide
+- `docs/SUMMARY.md`: Updated to include `IMPORT.md`
+- `README.md`: Badge corrections, header cleanup, removed unverified bundle size claims
+
+### 🆕 GitHub Actions / Gitea Workflows
+
+- Added `.gitea/workflows/npm.yml` for automatic npm package publishing to Gitea Packages on `v*` tags
+- Requires `GITEA_USER` and `PAT` secrets
+
+### 🧪 Tests
+
+- **Result: 9 suites · 101 passed · 4 skipped · 1 todo**
+- All lint and typecheck clean
+
+---
+
 ## v3.0.2 (Current) - 2026-05-19 — Bug Fix, Security & API Expansion
 
 ### 🐛 Bug Fixes

package/markdown/IMPORT.md

@@ -0,0 +1,139 @@
+# Classic `import` support
+
+Memorio supports two equivalent styles: the original global side-effect import,
+and the new named exports. Both share the same instances (one source of truth).
+
+```typescript
+// Global style (original)
+import 'memorio'
+state.user = { name: 'Sara' }
+
+// Classic import style (new)
+import { state } from 'memorio'
+state.user = { name: 'Sara' }
+```
+
+`state` in both examples is the exact same Proxy object.
+
+---
+
+## Why two styles?
+
+| Style | When to use |
+|-------|-------------|
+| `import 'memorio'` | Zero-config, global access everywhere, legacy scripts |
+| `import { state } from 'memorio'` | Explicit dependencies, tree-shakeable bundles, TypeScript IntelliSense |
+
+---
+
+## ESM named imports
+
+All modules are available as named exports:
+
+```typescript
+import {
+  state,
+  store,
+  session,
+  cache,
+  idb,
+  observer,
+  useObserver,
+  dispatch,
+  message,
+  devtools,
+  logger
+} from 'memorio'
+```
+
+Platform helpers:
+
+```typescript
+import {
+  isBrowser,
+  isNode,
+  isDeno,
+  isEdge,
+  getCapabilities,
+  createContext,
+  listContexts,
+  deleteContext
+} from 'memorio'
+```
+
+Internal utilities (for tests/debug):
+
+```typescript
+import internal, { propertyName } from 'memorio'
+import { setContext, getContext } from 'memorio'
+```
+
+Default export (the public `memorio` namespace):
+
+```typescript
+import memorio from 'memorio'
+memorio.help()
+```
+
+---
+
+## CJS usage
+
+```javascript
+const { state, store, memorio } = require('memorio')
+```
+
+---
+
+## React / useObserver
+
+`useObserver` works the same way via named import:
+
+```tsx
+import { useObserver, state } from 'memorio'
+
+function Counter() {
+  const [, forceUpdate] = useReducer(x => x + 1, 0)
+
+  useObserver(forceUpdate, [state.counter])
+
+  return <div>Count: {state.counter}</div>
+}
+```
+
+---
+
+## Context isolation
+
+```typescript
+import { createContext, listContexts, deleteContext, isolate } from 'memorio'
+
+const ctx = createContext('tenant-123')
+ctx.state.user = { name: 'Isolated' }
+ctx.store.set('settings', { theme: 'dark' })
+
+listContexts() // ['tenant-123']
+deleteContext('tenant-123')
+```
+
+---
+
+## Same-instance guarantee
+
+Named exports point to the same instances published on `globalThis` by
+`core/global` at bootstrap. Mutating via named export mutates the global,
+and vice versa.
+
+```typescript
+import { state } from 'memorio'
+
+state.importedFlag = true
+console.debug(globalThis.state.importedFlag) // true
+```
+
+---
+
+## Migration from global-only
+
+No code changes required. Existing `import 'memorio'` + `state.foo = 1`
+continues to work unchanged. Named exports are additive.

package/markdown/PLATFORM.md

@@ -41,8 +41,8 @@ Memorio automatically detects the environment on import:
 import 'memorio';
 
 // Check current platform
-console.debug(memorio.platform);   // 'browser' | 'node' | 'deno' | 'edge'
-console.debug(memorio.isPersistent); // true if using real storage
+console.debug(memorio.getCapabilities().platform); // 'browser' | 'node' | 'deno' | 'edge'
+console.debug(store.isPersistent); // true if using real localStorage
 ```
 
 ### Available Platform APIs
@@ -257,5 +257,9 @@ Same as browser - localStorage and sessionStorage are available.
 | Property | Type | Description |
 |----------|------|-------------|
 | `memorio.version` | `string` | Memorio version |
-| `memorio.platform` | `string` | Current platform |
+| `memorio.getCapabilities().platform` | `string` | Current platform |
+| `memorio.isBrowser()` / `isNode()` / `isDeno()` / `isEdge()` | `boolean` | Platform checks |
 | `memorio._sessionId` | `string` | Unique session identifier |
+
+> **Classic `import`**: context APIs are also named exports.
+> `import { createContext, listContexts, deleteContext, isolate } from 'memorio'`.

package/markdown/STATE.md

@@ -16,6 +16,9 @@ import 'memorio';
 
 That's it. `state` is now global.
 
+> **Classic `import`**: `state` is also a named export.
+> `import { state } from 'memorio'` returns the exact same proxy as `globalThis.state`.
+
 ---
 
 ## Quick Examples

package/markdown/STORE.md

@@ -15,6 +15,9 @@ npm install memorio
 import 'memorio';
 ```
 
+> **Classic `import`**: `store` is also a named export.
+> `import { store } from 'memorio'` returns the exact same instance as `globalThis.store`.
+
 ---
 
 ## Quick Examples

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "memorio",
   "codeName": "memorio",
-  "version": "4.5.3",
+  "version": "4.6.4",
   "description": "Memorio, State + Observer, Store and iDB for an easy life - Cross-platform compatible",
   "main": "./index.cjs",
   "browser": "./index.js",

package/types/exports.d.ts

@@ -0,0 +1,58 @@
+/**
+ * Named exports for classic `import` usage.
+ *
+ * Every export below points to the exact same instance
+ * already defined on globalThis by the core modules.
+ * `import { state } from 'memorio'` === `globalThis.state`.
+ *
+ * @see index.ts (runtime re-export)
+ */
+
+/// <reference path="./memorio.d.ts" />
+/// <reference path="./state.d.ts" />
+/// <reference path="./store.d.ts" />
+/// <reference path="./session.d.ts" />
+/// <reference path="./cache.d.ts" />
+/// <reference path="./idb.d.ts" />
+/// <reference path="./observer.d.ts" />
+/// <reference path="./useObserver.d.ts" />
+
+export const memorio: _memorio
+export const state: _state
+export const store: _store
+export const session: _session
+export const cache: _cache
+export const idb: _idb
+export const observer: _observer
+export const useObserver: _useObserver
+export const dispatch: _dispatch
+export const events: Record<string, any>
+
+export const isBrowser: () => boolean
+export const isNode: () => boolean
+export const isDeno: () => boolean
+export const isEdge: () => boolean
+export const getCapabilities: (...args: unknown[]) => any
+export const createContext: _memorio['createContext']
+export const listContexts: _memorio['listContexts']
+export const deleteContext: _memorio['deleteContext']
+export const isolate: _memorio['isolate']
+export const message: (...args: unknown[]) => void
+export const help: () => void
+
+export const propertyName: (container: any, object: any) => string | null
+export const internal: {
+  debug: boolean
+  tracking: boolean
+  trackedPaths: Set<string>
+  locked: boolean
+  lastAccessedPath: string
+  stateVersion: number
+  currentContext: string | null
+  clearTrackedPaths(): void
+  bumpStateVersion(): number
+}
+export const setContext: (id: string) => void
+export const getContext: () => string | null
+
+export default memorio

package/CODE_OF_CONDUCT.md

@@ -1,108 +0,0 @@
-# Code of Conduct — memorio
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to make participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, 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.
-
-## 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
-* 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
-
-## Our Responsibilities
-
-Project maintainers 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.
-
-Project maintainers 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 at <dariopassariello@gmail.com>.
-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.

package/CONTRIBUTING.md

@@ -1,105 +0,0 @@
-# Contributing
-
-First off, thanks for taking the time to contribute!
-
-All types of contributions are encouraged and valued. See the [Table of Contents](contributing.md#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions.
-
-> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
->
-> * Star the project
-> * Tweet about it
-> * Refer this project in your project's readme
-> * Mention the project at local meetups and tell your friends/colleagues
-
-## Table of Contents
-
-* [Code of Conduct](contributing.md#code-of-conduct)
-* [I Have a Question](contributing.md#i-have-a-question)
-  * [I Want To Contribute](contributing.md#i-want-to-contribute)
-  * [Reporting Bugs](contributing.md#reporting-bugs)
-  * [Suggesting Enhancements](contributing.md#suggesting-enhancements)
-  * [Your First Code Contribution](contributing.md#your-first-code-contribution)
-  * [Improving The Documentation](contributing.md#improving-the-documentation)
-* [Style guides](contributing.md#styleguides)
-  * [Commit Messages](contributing.md#commit-messages)
-* [Join The Project Team](contributing.md#join-the-project-team)
-
-## Code of Conduct
-
-This project and everyone participating in it is governed by the [memorio Code of Conduct](https://github.com/picla-net/picla.npm.memorio/blob/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [dariopassariello@gmail.com](mailto:dariopassariello@gmail.com).
-
-## I Have a Question
-
-Before you ask a question, it is best to search for existing [Issues](https://github.com/picla-net/picla.npm.memorio/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
-
-If you then still feel the need to ask a question and need clarification, we recommend the following:
-
-* Open an [Issue](https://github.com/picla-net/picla.npm.memorio/issues/new).
-* Provide as much context as you can about what you're running into.
-* Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
-
-We will then take care of the issue as soon as possible.
-
-## I Want To Contribute
-
-> ### Legal Notice
->
-> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
-
-### Reporting Bugs
-
-#### Before Submitting a Bug Report
-
-A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
-
-* Make sure that you are using the latest version.
-* Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment
-* To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/picla-net/picla.npm.memorio/issues?q=label%3Abug).
-* Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
-* Collect information about the bug:
-  * Stack trace (Traceback)
-  * OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
-  * Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
-  * Possibly your input and the output
-  * Can you reliably reproduce the issue? And can you also reproduce it with older versions?
-
-#### How Do I Submit a Good Bug Report?
-
-> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to [dariopassariello@gmail.com](mailto:dariopassariello@gmail.com).
-
-We use GitHub issues to track bugs and errors. If you run into an issue with the project:
-
-* Open an [Issue](https://github.com/picla-net/picla.npm.memorio/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
-* Explain the behavior you would expect and the actual behavior.
-* Please provide as much context as possible and describe the _reproduction steps_ that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
-* Provide the information you collected in the previous section.
-
-Once it's filed:
-
-* The project team will label the issue accordingly.
-* A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
-* If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](contributing.md#your-first-code-contribution).
-
-### Suggesting Enhancements
-
-This section guides you through submitting an enhancement suggestion for memorio, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
-
-#### Before Submitting an Enhancement
-
-* Make sure that you are using the latest version.
-* Perform a [search](https://github.com/picla-net/picla.npm.memorio/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
-* Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
-
-#### How Do I Submit a Good Enhancement Suggestion?
-
-Enhancement suggestions are tracked as [GitHub issues](https://github.com/picla-net/picla.npm.memorio/issues).
-
-* Use a **clear and descriptive title** for the issue to identify the suggestion.
-* Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
-* **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
-* You may want to **include screenshots or screen recordings** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [screentogif](https://www.screentogif.com/) to record GIFs on macOS and Windows, and the built-in [screen recorder in GNOME](https://help.gnome.org/users/gnome-help/stable/screen-shot-record.html.en) or [SimpleScreenRecorder](https://github.com/MaartenBaert/ssr) on Linux.
-* **Explain why this enhancement would be useful** to most boilerplate users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
-
-## Join The Project Team
-
-Please send email to <dariopassariello@gmail.com>

package/COPYRIGHT.md

@@ -1,6 +0,0 @@
-# Copyright
-
-Copyright (c) 2025, Dario Passariello. All rights reserved.
-<https://dario.passariello.ca>
-
-This software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.

package/LICENSE.md

@@ -1,21 +0,0 @@
-# MIT License
-
-Copyright (c) 2025 Dario Passariello
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/SECURITY.md

@@ -1,48 +0,0 @@
-# Security
-
-Memorio follows NIST and NSA security standards at the enterprise level.
-
-## Security Standards
-
-- **NIST Guidelines**: Follows NIST SP 800-53 security controls and NIST Cybersecurity Framework
-- **NSA Standards**: Defense-grade security practices; considers nation-state level threats in risk assessment
-
-## Supply Chain Security
-
-- **Socket.dev**: Minimum target score 90%; all alarms must be resolved before release
-- **Dependency Management**: Zero production dependencies (fully dependency-free); dev dependencies audited regularly
-- **Prohibited**: No `eval()` usage, no encrypted/obfuscated code in builds, no hardcoded secrets
-
-## Code Security
-
-- No hardcoded credentials or API keys
-- Secure random session ID generation (`crypto.randomUUID` → `crypto.getRandomValues` → fallback)
-- Input validation on all public APIs
-- XSS prevention on DevTools data export
-- Property-based access control on global objects (`Object.defineProperty` with `enumerable: false`)
-
-## OWASP Compliance
-
-Addresses OWASP Top 10 (2021):
-- A01:2021 — Broken Access Control (global object protection, property locks)
-- A02:2021 — Cryptographic Failures (crypto.randomUUID for session IDs)
-- A03:2021 — Injection (CSS sanitization in devtools)
-- A05:2021 — Security Misconfiguration (minimal surface area, no bundled secrets)
-- A06:2021 — Vulnerable and Outdated Components (regular npm audit, Socket.dev)
-- A07:2021 — Identification and Authentication Failures (N/A — library, no auth)
-- A08:2021 — Software and Data Integrity Failures (strict tsconfig, lock files)
-- A09:2021 — Security Logging and Monitoring Failures (DevTools inspect, Logger module)
-- A10:2021 — Server-Side Request Forgery (N/A — no network requests)
-
-## Reporting Security Issues
-
-If you find a security vulnerability:
-
-1. Email [Dario Passariello](mailto:dariopassarielloa@gmail.com)
-2. Or visit https://dario.passariello.ca/contact/
-
-Do not open public issues for security vulnerabilities.
-
----
-*Document version: 2.0 — Last updated: 2026-05-19*
-*Owner: BigLogic Security Team*