Remixer v3 and Scraper by yghaemi · Pull Request #782 · LibreTexts/conductor

yghaemi · 2026-04-27T16:52:32Z

No description provided.

…tion and expansion

…opups and responsive design

+
+  const getSupportCenterHref = () => {
+    // Always nav to main commons in production, otherwise use the current origin (e.g. development)
+    if (window.location.origin.endsWith("libretexts.org")) {


+
+  const getStoreHref = () => {
+    // Always nav to main store in production, otherwise use the current origin (e.g. development)
+    if (window.location.origin.endsWith("libretexts.org")) {


aikido-pr-checks · 2026-04-27T16:54:40Z

+      const existingAuthor = await Author.findOne({
+        email,
+        isAdminEntry: false,
+        orgID: process.env.ORG_ID,
+      });


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Show fix

Suggested change

const existingAuthor = await Author.findOne({

email,

isAdminEntry: false,

orgID: process.env.ORG_ID,

});

const existingAuthor = await Author.findOne({

email: { $eq: email },

isAdminEntry: false,

orgID: process.env.ORG_ID,

});

_{More info}

aikido-pr-checks · 2026-04-27T16:54:41Z

-    await authorService.deleteAuthor(req.params.id);
+    const { firstName, lastName, email, primaryInstitution, url } = req.body;
+    await Author.updateOne(
+      { _id: req.params.id, orgID: process.env.ORG_ID },


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

{ _id: req.params.id, orgID: process.env.ORG_ID },

{ _id: { $eq: req.params.id }, orgID: process.env.ORG_ID },

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-27T16:54:42Z

+    await Author.deleteOne({
+      _id: req.params.id,
+      orgID: process.env.ORG_ID,
+    }).orFail();


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Show fix

Suggested change

await Author.deleteOne({

_id: req.params.id,

orgID: process.env.ORG_ID,

}).orFail();

await Author.deleteOne({

_id: { $eq: req.params.id },

orgID: process.env.ORG_ID,

}).orFail();

_{More info}

aikido-pr-checks · 2026-04-27T16:54:46Z

+  subdomain,
+}: RunRemixerJobParams) => {
+  const job = await PrejectRemixerJob.findOne({ jobID }).sort({ _id: -1 });
+  const remixerState = await PrejectRemixer.findOne({ projectID }).sort({ _id: -1 });


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

const remixerState = await PrejectRemixer.findOne({ projectID }).sort({ _id: -1 });

const remixerState = await PrejectRemixer.findOne({ projectID: { $eq: projectID } }).sort({ _id: -1 });

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-27T16:54:48Z

+  Project.findOne({
+    projectID: req.body.projectID,
+  }).lean().then((project) => {


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

Project.findOne({

projectID: req.body.projectID,

}).lean().then((project) => {

Project.findOne({

projectID: { $eq: req.body.projectID },

}).lean().then((project) => {

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-27T16:54:49Z

+          return Task.findOne({
+            taskID: req.body.parent,
+          }).lean();


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

return Task.findOne({

taskID: req.body.parent,

}).lean();

return Task.findOne({

taskID: { $eq: req.body.parent },

}).lean();

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-27T16:54:50Z

+        return Task.updateOne({
+          taskID: task.taskID,
+        }, updateObj);


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

return Task.updateOne({

taskID: task.taskID,

}, updateObj);

return Task.updateOne({

taskID: { $eq: task.taskID },

}, updateObj);

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-27T16:54:51Z

+  Project.findOne({
+    projectID: req.query.projectID,
+  }).lean().then((project) => {


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Show fix

Remediation: User input should be validated (e.g. with class-validator, zod or joi) or sanitized (e.g. with mongo-sanitize). Alternatively cast request parameters to their expected type or use the $eq operator to block object injection. You can also Autofix all instances of NoSQL injection by installing Zen for Node.js.

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-27T16:54:52Z

+async function appendPressbooksJobMessages(jobID: string, messages: string[]) {
+  if (!messages.length) return;
+  await PressbooksImportJob.updateOne(
+    { jobID },


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Show fix

Remediation: User input should be validated (e.g. with class-validator, zod or joi) or sanitized (e.g. with mongo-sanitize). Alternatively cast request parameters to their expected type or use the $eq operator to block object injection. You can also Autofix all instances of NoSQL injection by installing Zen for Node.js.

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-27T16:54:53Z

+    resolve(Task.findOne({
+      taskID,
+    }).lean());


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

resolve(Task.findOne({

taskID,

}).lean());

resolve(Task.findOne({

taskID: { $eq: taskID },

}).lean());

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-27T16:54:54Z

+      return Project.findOne({
+        projectID: taskData.projectID,
+      }).lean();


NoSQL injection attack possible - high severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

return Project.findOne({

projectID: taskData.projectID,

}).lean();

return Project.findOne({

projectID: { $eq: taskData.projectID },

}).lean();

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-27T16:54:55Z

13 Open source vulnerabilities detected - critical severity
Aikido detected 13 vulnerabilities across 4 packages, it includes 2 critical and 11 high vulnerabilities.

Details

Remediation Aikido suggests bumping the vulnerable packages to a safe version.

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
More info

aikido-pr-checks · 2026-04-27T16:54:56Z

CVE-2026-2391

CVE-2026-2391 in qs - high severity

Summary

The arrayLimit option in qs does not enforce limits for comma-separated values when comma: true is enabled, allowing attackers to cause denial-of-service via memory exhaustion. This is a bypass of the array limit enforcement, similar to the bracket notation bypass addressed in GHSA-6rw7-vpxm-498p (CVE-2025-15284).

Details

When the comma option is set to true (not the default, but configurable in applications), qs allows parsing comma-separated strings as arrays (e.g., ?param=a,b,c becomes ['a', 'b', 'c']). However, the limit check for arrayLimit (default: 20) and the optional throwOnLimitExceeded occur after the comma-handling logic in parseArrayValue, enabling a bypass. This permits creation of arbitrarily large arrays from a single parameter, leading to excessive memory allocation.

Vulnerable code (lib/parse.js: lines ~40-50):

if (val && typeof val === 'string' && options.comma && val.indexOf(',') > -1) { return val.split(','); } if (options.throwOnLimitExceeded && currentArrayLength >= options.arrayLimit) { throw new RangeError('Array limit exceeded. Only ' + options.arrayLimit + ' element' + (options.arrayLimit === 1 ? '' : 's') + ' allowed in an array.'); } return val;

The split(',') returns the array immediately, skipping the subsequent limit check. Downstream merging via utils.combine does not prevent allocation, even if it marks overflows for sparse arrays.This discrepancy allows attackers to send a single parameter with millions of commas (e.g., ?param=,,,,,,,,...), allocating massive arrays in memory without triggering limits. It bypasses the intent of arrayLimit, which is enforced correctly for indexed (a[0]=) and bracket (a[]=) notations (the latter fixed in v6.14.1 per GHSA-6rw7-vpxm-498p).

PoC

Test 1 - Basic bypass:

npm install qs

const qs = require('qs'); const payload = 'a=' + ','.repeat(25); // 26 elements after split (bypasses arrayLimit: 5) const options = { comma: true, arrayLimit: 5, throwOnLimitExceeded: true }; try { const result = qs.parse(payload, options); console.log(result.a.length); // Outputs: 26 (bypass successful) } catch (e) { console.log('Limit enforced:', e.message); // Not thrown }

Configuration:

comma: true

arrayLimit: 5

throwOnLimitExceeded: true

Expected: Throws "Array limit exceeded" error.
Actual: Parses successfully, creating an array of length 26.

Impact

Denial of Service (DoS) via memory exhaustion.

Details

Remediation Aikido suggests bumping this package to version 6.14.2 to resolve this issue

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
More info

…rvice

aikido-pr-checks · 2026-04-28T14:19:19Z

+    title: 1,
+    _id: 0,
+  };
+  const project = await Project.findOne({ projectID: id }, projection);


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

const project = await Project.findOne({ projectID: id }, projection);

const project = await Project.findOne({ projectID: { $eq: id } }, projection);

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-28T14:19:20Z

+  const actorUUID = (req as any).user?.decoded?.uuid ?? "";
+
+  const project = await Project.findOne(
+    { projectID: id },


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

{ projectID: id },

{ projectID: { $eq: id } },

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-28T14:19:21Z

+  }
+
+  const remixerState = await PrejectRemixer.findOneAndUpdate(
+    { projectID: id, archived: false },


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

{ projectID: id, archived: false },

{ projectID: { $eq: id }, archived: false },

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-28T14:19:23Z

+    });
+  }
+
+  await PrejectRemixer.deleteOne({ projectID: id });


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

await PrejectRemixer.deleteOne({ projectID: id });

await PrejectRemixer.deleteOne({ projectID: { $eq: id } });

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

aikido-pr-checks · 2026-04-28T14:19:25Z

@@ -1334,8 +1350,7 @@ async function deleteTicket(
 ) {
  try {
    const { uuid } = req.params;
-    const ticketService = new SupportTicketService();
-    await ticketService.deleteTicket(uuid);
+    await SupportTicket.deleteOne({ uuid });


NoSQL injection attack possible - critical severity
Query injection attacks are possible if users can pass objects instead of strings to query functions such as findOne.

By injecting query operators attackers can control the behavior of the query, allowing them to bypass access controls and extract unauthorized data. Consider the attack payload ?user_id[$ne]=5: if the user_id query parameter is passed to the query function without validation or casting its type, an attacker can pass {$ne: 5} instead of an integer to the query. {$ne: 5} uses the 'not equal to' operator to access data of other users.

While this vulnerability is known as NoSQL injection, relational databases (mysql, postgres) are also vulnerable to this attack if the query library offers a NoSQL-like API and supports string-typed query operators. Examples include prisma and sequelize versions prior to 4.12.0.

Suggested change

await SupportTicket.deleteOne({ uuid });

await SupportTicket.deleteOne({ uuid: { $eq: uuid } });

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.}
_{More info}

jakeaturner · 2026-05-07T18:35:11Z

Superceded by #785

yghaemi added 7 commits March 3, 2026 14:12

feat: scraper UI and API and util

dc487e0

feat: pressbooks scraper, import to library

afb92c3

feat: enhance ImportWorkbenchModal with job tracking and status updates

33cee9d

feat: remixer v3

563543d

feat(book-import): add BookImportModal for importing pages with selec…

bf1c8ce

…tion and expansion

feat(remixer): enhance ProjectLinkButtons and ControlPanel with new p…

c9e5ae9

…opups and responsive design

refactor(api): remove deprecated /tt/:lib route and associated logic

138286d

yghaemi requested a review from jakeaturner April 27, 2026 16:52

github-advanced-security AI found potential problems Apr 27, 2026

View reviewed changes

aikido-pr-checks Bot reviewed Apr 27, 2026

View reviewed changes

yghaemi added 2 commits April 27, 2026 13:42

refactor(api): update remixer project API calls and remove authkey se…

2bfc245

…rvice

fix(api): remove unused authkey import from remixer service

6ebcf59

jakeaturner changed the base branch from master to staging April 27, 2026 21:16

aikido-pr-checks Bot reviewed Apr 28, 2026

View reviewed changes

jakeaturner closed this May 7, 2026

	{ _id: req.params.id, orgID: process.env.ORG_ID },
	{ _id: { $eq: req.params.id }, orgID: process.env.ORG_ID },

	const remixerState = await PrejectRemixer.findOne({ projectID }).sort({ _id: -1 });
	const remixerState = await PrejectRemixer.findOne({ projectID: { $eq: projectID } }).sort({ _id: -1 });

	const project = await Project.findOne({ projectID: id }, projection);
	const project = await Project.findOne({ projectID: { $eq: id } }, projection);

	{ projectID: id, archived: false },
	{ projectID: { $eq: id }, archived: false },

	await PrejectRemixer.deleteOne({ projectID: id });
	await PrejectRemixer.deleteOne({ projectID: { $eq: id } });

	await SupportTicket.deleteOne({ uuid });
	await SupportTicket.deleteOne({ uuid: { $eq: uuid } });

Conversation

yghaemi commented Apr 27, 2026

Uh oh!

aikido-pr-checks Bot Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 27, 2026

Choose a reason for hiding this comment

Summary

Details

PoC

Impact

Uh oh!

aikido-pr-checks Bot Apr 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aikido-pr-checks Bot Apr 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jakeaturner commented May 7, 2026

Uh oh!

Reviewers

Assignees

Labels

aikido-pr-checks Bot Apr 27, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 27, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 27, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 27, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 27, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 27, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 27, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 27, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 27, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 28, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 28, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 28, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 28, 2026 •

edited

Loading

aikido-pr-checks Bot Apr 28, 2026 •

edited

Loading