@agenttrail/guardrails 0.2.2 → 0.2.3

package/dist/guardrails.d.cts

@@ -1,5 +1,5 @@
-import { MatchCondition, Fixture, Rule } from './schema.cjs';
-export { Action, FixtureInput, Fixtures, Match, RuleInput, Severity } from './schema.cjs';
+import { M as MatchCondition, F as Fixture, R as Rule } from './schema-BRdYtWjP.cjs';
+export { A as Action, a as FixtureInput, b as Fixtures, c as Match, O as OWASP_AGENTIC, d as OWASP_IDS, e as OWASP_LLM, f as OWASP_SOURCES, g as OwaspId, h as OwaspRisk, i as RuleInput, S as Severity, j as isOwaspId, o as owaspIndex, k as owaspTitle } from './schema-BRdYtWjP.cjs';
 import 'zod';
 
 /**
@@ -365,7 +365,7 @@ declare function mentions(text: string): Fixture[];
  * Pinned to `package.json`'s `version` by `__tests__/stamp.test.ts` — this is a copy
  * of that value, not an independent one, and the test is what makes the copy safe.
  */
-declare const CATALOG_VERSION = "0.2.2";
+declare const CATALOG_VERSION = "0.2.3";
 /**
  * When the rules in this catalog reached their current state, as an ISO-8601
  * instant. The question it answers is not "when did this reach a registry" but "how
@@ -375,7 +375,7 @@ declare const CATALOG_VERSION = "0.2.2";
  * the guard handles a missing date, and a wrong date that looks right is worse than
  * a missing one.
  */
-declare const CATALOG_PUBLISHED_AT = "2026-10-06T13:41:00Z";
+declare const CATALOG_PUBLISHED_AT = "2026-10-15T18:58:34Z";
 
 /**
  * The corpus itself — rules only, and **deliberately free of zod**.
@@ -388,8 +388,8 @@ declare const CATALOG_PUBLISHED_AT = "2026-10-06T13:41:00Z";
  *
  * The package ROOT cannot satisfy that: `index.ts` re-exports `./schema.js`, which
  * value-imports zod. So the guard imports `@agenttrail/guardrails/guardrails` — this
- * file — whose whole import graph is `./packs.js`, `./exemptions.js` and
- * `./fixtures.js` (all three plain data) plus a TYPE-only
+ * file — whose whole import graph is `./packs.js`, `./exemptions.js`, `./fixtures.js`
+ * and `./owasp.js` (all four plain data) plus a TYPE-only
  * reference to `./schema.js`, which esbuild erases. Everyone else keeps using the
  * root and gets the schema with it.
  *

package/dist/guardrails.d.ts

@@ -1,5 +1,5 @@
-import { MatchCondition, Fixture, Rule } from './schema.js';
-export { Action, FixtureInput, Fixtures, Match, RuleInput, Severity } from './schema.js';
+import { M as MatchCondition, F as Fixture, R as Rule } from './schema-BRdYtWjP.js';
+export { A as Action, a as FixtureInput, b as Fixtures, c as Match, O as OWASP_AGENTIC, d as OWASP_IDS, e as OWASP_LLM, f as OWASP_SOURCES, g as OwaspId, h as OwaspRisk, i as RuleInput, S as Severity, j as isOwaspId, o as owaspIndex, k as owaspTitle } from './schema-BRdYtWjP.js';
 import 'zod';
 
 /**
@@ -365,7 +365,7 @@ declare function mentions(text: string): Fixture[];
  * Pinned to `package.json`'s `version` by `__tests__/stamp.test.ts` — this is a copy
  * of that value, not an independent one, and the test is what makes the copy safe.
  */
-declare const CATALOG_VERSION = "0.2.2";
+declare const CATALOG_VERSION = "0.2.3";
 /**
  * When the rules in this catalog reached their current state, as an ISO-8601
  * instant. The question it answers is not "when did this reach a registry" but "how
@@ -375,7 +375,7 @@ declare const CATALOG_VERSION = "0.2.2";
  * the guard handles a missing date, and a wrong date that looks right is worse than
  * a missing one.
  */
-declare const CATALOG_PUBLISHED_AT = "2026-10-06T13:41:00Z";
+declare const CATALOG_PUBLISHED_AT = "2026-10-15T18:58:34Z";
 
 /**
  * The corpus itself — rules only, and **deliberately free of zod**.
@@ -388,8 +388,8 @@ declare const CATALOG_PUBLISHED_AT = "2026-10-06T13:41:00Z";
  *
  * The package ROOT cannot satisfy that: `index.ts` re-exports `./schema.js`, which
  * value-imports zod. So the guard imports `@agenttrail/guardrails/guardrails` — this
- * file — whose whole import graph is `./packs.js`, `./exemptions.js` and
- * `./fixtures.js` (all three plain data) plus a TYPE-only
+ * file — whose whole import graph is `./packs.js`, `./exemptions.js`, `./fixtures.js`
+ * and `./owasp.js` (all four plain data) plus a TYPE-only
  * reference to `./schema.js`, which esbuild erases. Everyone else keeps using the
  * root and gets the schema with it.
  *

package/dist/guardrails.js

@@ -23,13 +23,26 @@ import {
   mentions,
   pwsh,
   rulesForPack
-} from "./chunk-GNN4TGRY.js";
+} from "./chunk-IQHM6BLL.js";
+import {
+  OWASP_AGENTIC,
+  OWASP_IDS,
+  OWASP_LLM,
+  OWASP_SOURCES,
+  isOwaspId,
+  owaspIndex,
+  owaspTitle
+} from "./chunk-LO4OCVQN.js";
 export {
   CATALOG_PUBLISHED_AT,
   CATALOG_VERSION,
   GIT_TEXT_MENTION,
   HTTP_BODY_MENTION,
   LEADING_FLAGS,
+  OWASP_AGENTIC,
+  OWASP_IDS,
+  OWASP_LLM,
+  OWASP_SOURCES,
   PACKS,
   PRINT_MENTION,
   QUOTED_MENTION,
@@ -40,6 +53,7 @@ export {
   bash,
   file,
   getRule,
+  isOwaspId,
   isPack,
   mcp,
   mentionInCommit,
@@ -47,6 +61,8 @@ export {
   mentionInPost,
   mentionInSearch,
   mentions,
+  owaspIndex,
+  owaspTitle,
   pwsh,
   rulesForPack
 };