@realchemistry/auth-guard@2.2.16
Sealed OIDC + PKCE chassis for Real Chemistry's Auth Hub. `auth-guard serve` runs the auth front door; consumer apps stay blind to OIDC and read identity from x-rc-user-* headers.
AI Security Review
scanned 6d ago · by lpm-firewall-aiSource confirms that postinstall mutates the consumer project's agent instructions and skill directory without an affirmative consent gate. This meets the policy for unconsented install-time mutation of a foreign AI-agent control surface.
Decision evidence
public snapshot- package.json runs scripts/install-skill.mjs from postinstall.
- The postinstall installer uses the consumer project root and copies package-provided agent skills into its .local/skills directory.
- The installer creates or updates the consumer root AGENTS.md with package-provided rules during postinstall.
- The bundled AGENTS snippet adds persistent instructions for agents working in the consumer project.
- The packed-consumer check confirms that installation creates AGENTS.md with the package marker.
- The installer provides AUTH_GUARD_SKIP_SKILL_INSTALL=1 as an opt-out and limits AGENTS.md replacement to a marked section.
Source & flagged code
3 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgSource creates an unconsented AI-agent control surface through install-time mutation or a default unauthenticated remote skill channel.
scripts/install-skill.mjsView on unpkg · L9A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/probe.js#virtual:normalized:round1View on unpkgFindings
Affected versions and remediation
This report applies to @realchemistry/auth-guard@2.2.16.
See all versions of @realchemistry/auth-guard for other recorded verdicts.
- Avoid installing @realchemistry/auth-guard@2.2.16. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.