registry / Telemetry / @soloworks/smking-next

@soloworks/smking-next

AI-native SEO (AEO) for Next.js — auto-inject JSON-LD, FAQ, AI summary, and SEO metadata so AI crawlers (ChatGPT, Perplexity, Google AI) can cite your pages.

This report shows the evidence for @soloworks/smking-next@0.23.2. 0 of 5 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 6d ago · by lpm-firewall-ai

The runtime proxy automatically reports observed site hosts and page paths when published-v2 reporting is configured. This is beyond basic package and runtime telemetry, and no disclosure of this collection was found in the README, so it warrants a warning.

Static reason

No blocking static signals were detected.

Trigger

A page request passes through smkingProxy while published-v2 mode is enabled and SMKING_WEBHOOK_SECRET is set.

Impact

The service receives site host and page-path observations without an explicit per-report user action.

Mechanism

The proxy schedules a throttled report containing the API key, host, SDK metadata, and request path, then POSTs it to the configured base URL at /api/v2/sdk/report.

AI rationale

Evidence

src/lib/proxy.tssrc/lib/report-v2.ts

Network endpoints1

<configured SMKING_BASE_URL>/api/v2/sdk/report

Decision evidence

public snapshot

AI called this Suspicious at 86.0% confidence as Unknown with medium false-positive risk.

Evidence for warning

When the proxy observes a page request under published-v2 mode, it schedules a report containing the site host and request path.
The report includes the API key and SDK metadata, then POSTs to the configured base URL at /api/v2/sdk/report.
Reporting is gated on SMKING_WEBHOOK_SECRET being set and is throttled per host and path for one minute.

Evidence against

The package has no install, preinstall, or postinstall lifecycle script.
The report uses the configured service base URL and signs its payload with the configured webhook secret.
The CLI's project edits happen only when its install subcommand is explicitly run.

Behavioral surface

Source

CryptoEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 30 file(s), 137 KB of source, external domains: getpagezero.com

Source & flagged code

5 flagged

src/lib/webhook-route.tsView file

•stage = ast_semantic_analysis; reason = ast_alias_growth_limit_exceeded; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

src/lib/webhook-route.tsView on unpkg

src/lib/proxy.tsView file

107if (usesPublishedV2() && isPageObservation(request)) { reportObservedPath({ apiKey, baseUrl, path: request.nextUrl.pathname, url: reques

Medium

Ai Review Evidence

When the proxy observes a page request under published-v2 mode, it schedules a report containing the site host and request path.

src/lib/proxy.tsView on unpkg · L107

src/lib/report-v2.tsView file

Findings

1 High6 Medium4 Low

HighSemantic Analysis Limitedsrc/lib/webhook-route.ts

MediumNetwork

MediumEnvironment Vars

MediumAi Review Evidencesrc/lib/proxy.ts

MediumAi Review Evidencesrc/lib/report-v2.ts

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to @soloworks/smking-next@0.23.2.

The versions list below shows the verdict for each recorded version.

Review the evidence and your use of @soloworks/smking-next@0.23.2 before allowing it. Restrict the permissions described in this report.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.

Evidence last updated: 2026-10-29 20:32:06.973Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

5 known versions

0.23.2latestshownSuspiciousTelemetryWarnPublishedOct 28, 2026, 10:36 AM 0.23.1Unknown—AllowUnder ReviewOct 7, 2026, 3:23 AM 0.21.6Clean—AllowPublishedJul 20, 2026, 2:19 PM 0.21.3Clean—AllowPublishedJul 3, 2026, 8:17 AM

registry / Telemetry / @soloworks/smking-next

@soloworks/smking-next

AI-native SEO (AEO) for Next.js — auto-inject JSON-LD, FAQ, AI summary, and SEO metadata so AI crawlers (ChatGPT, Perplexity, Google AI) can cite your pages.

This report shows the evidence for @soloworks/smking-next@0.23.2. 0 of 5 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 6d ago · by lpm-firewall-ai

Static reason

No blocking static signals were detected.

Trigger

A page request passes through smkingProxy while published-v2 mode is enabled and SMKING_WEBHOOK_SECRET is set.

Impact

The service receives site host and page-path observations without an explicit per-report user action.

Mechanism

The proxy schedules a throttled report containing the API key, host, SDK metadata, and request path, then POSTs it to the configured base URL at /api/v2/sdk/report.

AI rationale

Evidence

src/lib/proxy.tssrc/lib/report-v2.ts

Network endpoints1

<configured SMKING_BASE_URL>/api/v2/sdk/report

Decision evidence

public snapshot

AI called this Suspicious at 86.0% confidence as Unknown with medium false-positive risk.

Evidence for warning

When the proxy observes a page request under published-v2 mode, it schedules a report containing the site host and request path.
The report includes the API key and SDK metadata, then POSTs to the configured base URL at /api/v2/sdk/report.
Reporting is gated on SMKING_WEBHOOK_SECRET being set and is throttled per host and path for one minute.

Evidence against

The package has no install, preinstall, or postinstall lifecycle script.
The report uses the configured service base URL and signs its payload with the configured webhook secret.
The CLI's project edits happen only when its install subcommand is explicitly run.

Behavioral surface

Source

CryptoEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 30 file(s), 137 KB of source, external domains: getpagezero.com

Source & flagged code

5 flagged

src/lib/webhook-route.tsView file

•stage = ast_semantic_analysis; reason = ast_alias_growth_limit_exceeded; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

src/lib/webhook-route.tsView on unpkg

src/lib/proxy.tsView file

107if (usesPublishedV2() && isPageObservation(request)) { reportObservedPath({ apiKey, baseUrl, path: request.nextUrl.pathname, url: reques

Medium

Ai Review Evidence

When the proxy observes a page request under published-v2 mode, it schedules a report containing the site host and request path.

src/lib/proxy.tsView on unpkg · L107

src/lib/report-v2.tsView file

Findings

1 High6 Medium4 Low

HighSemantic Analysis Limitedsrc/lib/webhook-route.ts

MediumNetwork

MediumEnvironment Vars

MediumAi Review Evidencesrc/lib/proxy.ts

MediumAi Review Evidencesrc/lib/report-v2.ts

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to @soloworks/smking-next@0.23.2.

The versions list below shows the verdict for each recorded version.

Review the evidence and your use of @soloworks/smking-next@0.23.2 before allowing it. Restrict the permissions described in this report.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.

Evidence last updated: 2026-10-29 20:32:06.973Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

5 known versions