supertokens-website@20.1.8
frontend sdk for website to be used for auth solution.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe authentication package and inspected dependency setup show no confirmed attack behavior. The shipped release helper contains an explicit review-directed endorsement, so this is malicious reviewer manipulation despite requiring a user to run the helper.
Decision evidence
public snapshot- The release helper pushes branches and creates pull requests when run.
- The helper posts a canned comment saying the release looks good to merge, which is a concrete attempt to influence review.
- The package manifest has no install lifecycle hook, so the helper requires explicit execution.
- The prepared browser lock dependency’s postinstall only prints a thank-you message.
- The override dependency entrypoint exports an override builder.
- The flagged release helper is not declared as a package entrypoint or lifecycle script.
- The inspected dependency setup shows no additional attack behavior.
Source & flagged code
4 flaggedPackage hides binary, compressed, or executable-looking payloads in test/fixture/hidden paths.
.release-staging/open-website-prs.shView on unpkgThe release helper pushes branches and creates pull requests when run.
.release-staging/open-website-prs.shView on unpkg · L6Package ships non-JavaScript build or shell helper files.
.release-staging/open-website-prs.shView on unpkgFindings
Affected versions and remediation
This report applies to supertokens-website@20.1.8.
See all versions of supertokens-website for other recorded verdicts.
- Avoid installing supertokens-website@20.1.8. 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.