registry / @soloworks/smking-next / 0.21.6
@soloworks/smking-next@0.21.6
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.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe scanner's sitemap finding is a package-aligned API request using the configured publishable key, not harvesting or exfiltration. Source inspection found no lifecycle execution or concrete malicious chain.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
User runs smking-next install/doctor or imports an exported Next.js integration.
Impact
The configured SaaS receives its publishable key and normal site/request metadata; no unconsented install-time execution or credential harvesting was found.
Mechanism
Opt-in SaaS SEO/CMS fetches and explicit route scaffolding.
AI rationale
The scanner's sitemap finding is a package-aligned API request using the configured publishable key, not harvesting or exfiltration. Source inspection found no lifecycle execution or concrete malicious chain.
Evidence
package.jsonbin/install.mjssrc/lib/sitemap.tssrc/lib/client.tssrc/lib/proxy.tssrc/components/smking-runtime.tsxapp/sitemap.tsapp/robots.tsapp/llms.txt/route.ts.env.env.local
Network endpoints4
getpagezero.com/api/v1/public/sitemap.xmlgetpagezero.com/api/v1/public/aeogetpagezero.com/api/v1/crawler-hitgetpagezero.com/api/v1/public/runtime.js
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- Explicit CLI can read .env/.env.local during user-invoked doctor.
- Runtime component can load SaaS-hosted runtime.js when explicitly rendered.
Evidence against
- package.json has no preinstall/install/postinstall lifecycle hook.
- bin/install.mjs only runs through the explicit smking-next command.
- CLI scaffold only creates missing Next.js route files; it never overwrites files.
- sitemap.ts sends the configured publishable API key only to the documented SaaS API.
- No shell execution, eval, dynamic code loading, or hidden persistence found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
2 flaggedsrc/lib/sitemap.tsView file
24* - `SMKING_API_KEY` (publishable, the `pk_…` key)
L25: * - `SMKING_BASE_URL` (defaults to https://getpagezero.com)
L26: */
L27: export default async function smkingSitemap(): Promise<MetadataRoute.Sitemap> {
L28: if (process.env.SMKING_DISABLE_TAKEOVER_SITEMAP === "1") return [];
L29: const apiKey = process.env.SMKING_API_KEY;
...
L32:
L33: let body: string;
L34: try {
...
L44: if (!res.ok) return [];
L45: body = await res.text();
L46: } catch {
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
src/lib/sitemap.tsView on unpkg · L2424Trigger-reachable chain: manifest.exports -> src/lib/sitemap.ts
L24: * - `SMKING_API_KEY` (publishable, the `pk_…` key)
L25: * - `SMKING_BASE_URL` (defaults to https://getpagezero.com)
L26: */
L27: export default async function smkingSitemap(): Promise<MetadataRoute.Sitemap> {
L28: if (process.env.SMKING_DISABLE_TAKEOVER_SITEMAP === "1") return [];
L29: const apiKey = process.env.SMKING_API_KEY;
...
L32:
L33: let body: string;
L34: try {
...
L44: if (!res.ok) return [];
L45: body = await res.text();
L46: } catch {
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
src/lib/sitemap.tsView on unpkg · L24Findings
2 Critical3 Medium4 Low
CriticalCredential Exfiltrationsrc/lib/sitemap.ts
CriticalTrigger Reachable Dangerous Capabilitysrc/lib/sitemap.ts
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @soloworks/smking-next@0.21.6.
See all versions of @soloworks/smking-next for other recorded verdicts.
- Review the evidence and your use of @soloworks/smking-next@0.21.6 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.