syntropylog 0.12.2 → 0.12.4

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.12.4
+
+### Patch Changes
+
+- **CI & native addon:** GitHub Actions (build-native, release, ci) now run `pnpm run build` in syntropylog-native so the post-build patch always runs: index.js (no execSync, resolveLddPathWithoutShell) and index.mjs (static require('./index.js'), no join/path/url). SECURITY.md documents fs module usage and native ESM entry; patch script also patches index.mjs when NAPI-RS generates dynamic require. ESLint: ignore syntropylog-native/scripts for Node CommonJS scripts.
+
+## 0.12.3
+
+### Patch Changes
+
+- **SECURITY.md:** Document supply-chain alerts that may appear on the **yaml** package: (1) **URLs** — documentation links only (caniuse, MDN), no runtime network requests; (2) **Behavioral (medium)** — stringify/serialization analysis, vendor states no malicious activity. Clarifies that SyntropyLog uses only `parse` with schema `json`.
+
 ## 0.12.2
 
 ### Patch Changes
@@ -8,6 +20,8 @@
 
   **Docs - Universal Adapter:** README section 3 reworked: mapping is defined once with `UniversalLogFormatter` (outside the executor); executor receives the mapped object and can send it to multiple backends (e.g. Prisma, TypeORM, Mongoose) in one block. Single example shows one mapping → one object → three destinations with `Promise.all`.
 
+- **YAML / supply chain:** Replaced **js-yaml** with **yaml** (eemeli/yaml). The new dependency has no external packages (no argparse), removing the transitive alerts for URLs, filesystem, and env vars that came from js-yaml’s CLI helper. `loadLoggerConfig` now uses `parse(..., { schema: 'json' })` for safe parsing.
+
 ## 0.12.0
 
 First release after 0.11.3. Includes all framework refinements validated end-to-end with the examples repo (0.11.4 was never published to npm).
@@ -159,7 +173,7 @@ _Nothing at the moment._
 
 ### Security
 
-- **loadLoggerConfig**: Use js-yaml's `JSON_SCHEMA` when parsing YAML files to avoid prototype pollution and dangerous types. Use only with configuration files under deployment team control.
+- **loadLoggerConfig**: Use the **yaml** package (eemeli/yaml) with schema `json` when parsing YAML files to avoid prototype pollution and dangerous types; **yaml** has no external dependencies (no argparse). Use only with configuration files under deployment team control.
 
 ### Fixed
 

package/CONTRIBUTING.md

@@ -88,27 +88,47 @@ We welcome code contributions! To contribute code, please follow these steps:
 
 ## Release process (maintainers)
 
-Guía detallada: [docs/PREPARAR_PUBLICACION.md](docs/PREPARAR_PUBLICACION.md).
+Detailed guide: [docs/PREPARAR_PUBLICACION.md](docs/PREPARAR_PUBLICACION.md) (Spanish).
 
-**Ramas auxiliares (feature, develop, etc.):** en cada push y en los PRs se ejecuta solo el workflow **CI** (lint, build, tests, benchmark con addon nativo). No se publica nada en npm. Así puedes validar que todo pase antes de integrar a `main`.
+**Feature and develop branches:** On every push and on PRs, only the **CI** workflow runs (lint, build, tests, benchmark with native addon). Nothing is published to npm. This lets you validate everything before merging into `main`.
 
-**Solo al hacer push a `main`** se ejecuta el workflow **Release** (build del addon en todas las plataformas y, si hay changesets, versionado/publicación en npm).
+**Only when pushing to `main`** does the **Release** workflow run (build the addon on all platforms and, if there are changesets, versioning/publishing to npm).
 
-Releases use [Changesets](https://github.com/changesets/changesets) and GitHub Actions. **Para que la versión suba en npm, siempre tienes que hacer una de estas dos cosas:**
+Releases use [Changesets](https://github.com/changesets/changesets) and GitHub Actions. **To have a new version published to npm, you must do one of the following:**
 
-### Opción A: Usar el PR que crea el action
+### Option A: Use the PR created by the action
 
-1. **Añade un changeset** al cambiar la librería: `pnpm changeset` (elige tipo de versión y describe el cambio).
-2. **Push a `main`**. El workflow crea un PR **"Version Packages"** con el bump (ej. 0.9.12 → 0.9.13) y el CHANGELOG actualizado. **Todavía no publica en npm.**
-3. **Mergea ese PR** en `main`. Ese merge vuelve a disparar el workflow y **ahí sí** se ejecuta `publish` y la nueva versión aparece en npm.
+1. **Add a changeset** when changing the library: `pnpm changeset` (choose version bump type and describe the change).
+2. **Push to `main`**. The workflow creates a **"Version Packages"** PR with the version bump (e.g. 0.9.12 → 0.9.13) and updated CHANGELOG. **Nothing is published to npm yet.**
+3. **Merge that PR** into `main`. That merge triggers the workflow again and **then** `publish` runs and the new version appears on npm.
 
-### Opción B: Subir la versión a mano (sin PR)
+### Option B: Bump the version manually (no PR)
 
-1. Con changesets ya en el repo, en local: `pnpm run version-packages`. Eso actualiza `package.json`, CHANGELOG y borra los changesets.
-2. **Commit** (package.json, CHANGELOG.md, y los .changeset/*.md borrados) y **push a `main`**.
-3. El workflow corre, no hay changesets que aplicar, y ejecuta **publish** → la versión sube a npm.
+1. With changesets already in the repo, run locally: `pnpm run version-packages`. This updates `package.json`, CHANGELOG, and removes the consumed changesets.
+2. **Commit** (package.json, CHANGELOG.md, and the removed .changeset/*.md files) and **push to `main`**.
+3. The workflow runs, there are no changesets to apply, and it runs **publish** → the new version is published to npm.
 
-En ambos casos, **main** y **npm** quedan con la misma versión.
+In both cases, **main** and **npm** end up with the same version.
+
+## Repository size and what not to commit
+
+The repo should stay small so clones are fast. The following are in `.gitignore` and **must not** be committed:
+
+- `node_modules/`, `dist/`, `coverage/`
+- `assets/` (images; the README uses an external logo URL)
+- `docs/`, `.cursor/`, `.turbo`
+
+**If `assets/` or `coverage/` are already tracked**, remove them from Git (files stay on disk, only tracking is removed). Check first with `git ls-files assets/ coverage/`; if that lists files, run:
+
+```bash
+git rm -r --cached assets/
+git rm -r --cached coverage/
+git commit -m "chore: stop tracking assets and coverage"
+```
+
+If the path is not tracked, `git rm --cached` will report "did not match any file(s)" — that’s expected; nothing to do.
+
+The clone size (~36 MB) is mostly **Git history** (old copies of heavy files). To reduce it you would need to rewrite history (e.g. `git filter-repo` or BFG to remove `assets/` from the past). That changes commit hashes and requires a force-push; only do it if the team agrees.
 
 ## Getting Help
 

package/dist/index.cjs

@@ -2397,8 +2397,8 @@ class ConsoleTransport extends Transport {
  * @file src/logger/transports/optionalChalk.ts
  * @description Built-in chalk-like API using ANSI escape codes. No chalk dependency.
  * Used by ClassicConsoleTransport, PrettyConsoleTransport, CompactConsoleTransport, ColorfulConsoleTransport.
- * Does not read process.env; pass disableColors from transport options (e.g. for NO_COLOR use
- * disableColors: process.env.NO_COLOR != null && process.env.NO_COLOR !== '' && process.env.NO_COLOR !== '0').
+ * This module does not read environment variables. Pass disableColors from transport options;
+ * to respect the NO_COLOR convention, set disableColors from your app (e.g. from the NO_COLOR env var). See SECURITY.md.
  */
 const RESET = '\x1b[0m';
 function wrap(s, codes) {
@@ -2450,9 +2450,8 @@ let cachedWithColors = null;
 let cachedNoColors = null;
 /**
  * Returns a chalk-like instance using built-in ANSI colors. No external chalk dependency.
- * Does not read process.env. Pass disableColors from transport options; when true, output has no colors.
- * When false, colors are used only if stdout is a TTY. To respect NO_COLOR, pass
- * disableColors: process.env.NO_COLOR != null && process.env.NO_COLOR !== '' && process.env.NO_COLOR !== '0'.
+ * Does not read environment variables. Pass disableColors from transport options; when true, output has no colors.
+ * When false, colors are used only if stdout is a TTY. To respect NO_COLOR, derive disableColors in your app and pass it here. See SECURITY.md.
  */
 function getOptionalChalk(disableColors) {
     if (disableColors) {

package/dist/index.d.ts

@@ -796,8 +796,8 @@ declare class ConsoleTransport extends Transport {
  * @file src/logger/transports/optionalChalk.ts
  * @description Built-in chalk-like API using ANSI escape codes. No chalk dependency.
  * Used by ClassicConsoleTransport, PrettyConsoleTransport, CompactConsoleTransport, ColorfulConsoleTransport.
- * Does not read process.env; pass disableColors from transport options (e.g. for NO_COLOR use
- * disableColors: process.env.NO_COLOR != null && process.env.NO_COLOR !== '' && process.env.NO_COLOR !== '0').
+ * This module does not read environment variables. Pass disableColors from transport options;
+ * to respect the NO_COLOR convention, set disableColors from your app (e.g. from the NO_COLOR env var). See SECURITY.md.
  */
 /** Chalk-like API: chainable style that returns wrapped string when called. */
 type ChalkLike = {

package/dist/index.mjs

@@ -2375,8 +2375,8 @@ class ConsoleTransport extends Transport {
  * @file src/logger/transports/optionalChalk.ts
  * @description Built-in chalk-like API using ANSI escape codes. No chalk dependency.
  * Used by ClassicConsoleTransport, PrettyConsoleTransport, CompactConsoleTransport, ColorfulConsoleTransport.
- * Does not read process.env; pass disableColors from transport options (e.g. for NO_COLOR use
- * disableColors: process.env.NO_COLOR != null && process.env.NO_COLOR !== '' && process.env.NO_COLOR !== '0').
+ * This module does not read environment variables. Pass disableColors from transport options;
+ * to respect the NO_COLOR convention, set disableColors from your app (e.g. from the NO_COLOR env var). See SECURITY.md.
  */
 const RESET = '\x1b[0m';
 function wrap(s, codes) {
@@ -2428,9 +2428,8 @@ let cachedWithColors = null;
 let cachedNoColors = null;
 /**
  * Returns a chalk-like instance using built-in ANSI colors. No external chalk dependency.
- * Does not read process.env. Pass disableColors from transport options; when true, output has no colors.
- * When false, colors are used only if stdout is a TTY. To respect NO_COLOR, pass
- * disableColors: process.env.NO_COLOR != null && process.env.NO_COLOR !== '' && process.env.NO_COLOR !== '0'.
+ * Does not read environment variables. Pass disableColors from transport options; when true, output has no colors.
+ * When false, colors are used only if stdout is a TTY. To respect NO_COLOR, derive disableColors in your app and pass it here. See SECURITY.md.
  */
 function getOptionalChalk(disableColors) {
     if (disableColors) {

package/dist/types/config/loadLoggerConfig.d.ts

@@ -35,7 +35,7 @@ export interface LoggerConfigLoaderOptions {
  * It does NOT read environment variables directly; all state must be passed via `opts`.
  * If no file is found, it returns an empty object, making the config file optional.
  *
- * **Security:** A restricted schema (JSON_SCHEMA) is used to avoid prototype pollution
+ * **Security:** A restricted schema (`json`) is used to avoid prototype pollution
  * and dangerous types. Only use with configuration files under deployment team
  * control (controlled paths and permissions). This function reads only the paths
  * derived from opts (configPath, configDir, defaultBase, environment); no other

package/dist/types/logger/transports/optionalChalk.d.ts

@@ -2,8 +2,8 @@
  * @file src/logger/transports/optionalChalk.ts
  * @description Built-in chalk-like API using ANSI escape codes. No chalk dependency.
  * Used by ClassicConsoleTransport, PrettyConsoleTransport, CompactConsoleTransport, ColorfulConsoleTransport.
- * Does not read process.env; pass disableColors from transport options (e.g. for NO_COLOR use
- * disableColors: process.env.NO_COLOR != null && process.env.NO_COLOR !== '' && process.env.NO_COLOR !== '0').
+ * This module does not read environment variables. Pass disableColors from transport options;
+ * to respect the NO_COLOR convention, set disableColors from your app (e.g. from the NO_COLOR env var). See SECURITY.md.
  */
 /** Chalk-like API: chainable style that returns wrapped string when called. */
 export type ChalkLike = {
@@ -23,8 +23,7 @@ export type ChalkLike = {
 };
 /**
  * Returns a chalk-like instance using built-in ANSI colors. No external chalk dependency.
- * Does not read process.env. Pass disableColors from transport options; when true, output has no colors.
- * When false, colors are used only if stdout is a TTY. To respect NO_COLOR, pass
- * disableColors: process.env.NO_COLOR != null && process.env.NO_COLOR !== '' && process.env.NO_COLOR !== '0'.
+ * Does not read environment variables. Pass disableColors from transport options; when true, output has no colors.
+ * When false, colors are used only if stdout is a TTY. To respect NO_COLOR, derive disableColors in your app and pass it here. See SECURITY.md.
  */
 export declare function getOptionalChalk(disableColors: boolean): ChalkLike;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "syntropylog",
-  "version": "0.12.2",
+  "version": "0.12.4",
   "engines": {
     "node": ">=20.0.0"
   },
@@ -140,7 +140,7 @@
     "provenance": true
   },
   "dependencies": {
-    "js-yaml": "^4.1.1"
+    "yaml": "^2.8.2"
   },
   "optionalDependencies": {
     "syntropylog-native": "0.1.0"
@@ -153,7 +153,6 @@
     "@rollup/plugin-json": "^6.1.0",
     "@rollup/plugin-node-resolve": "^16.0.0",
     "@rollup/plugin-typescript": "^12.1.2",
-    "@types/js-yaml": "^4.0.9",
     "@types/node": "^22.13.5",
     "@typescript-eslint/eslint-plugin": "8.56.1",
     "@typescript-eslint/parser": "8.56.1",