Docs & Rules

dromara/Sa-TokenGitHubLast refreshed Oct 2, 2026

This is a public, read-only report. Striff reads this repository's docs, turns each sentence that makes a claim about the code into a rule, and checks the rule against the code on the default branch. How this works

1 name in these docs no longer matches the code.

dev1100c7clisted 17h ago

Is this yours? Install to manage it

Once installed, Striff checks every pull request.

7
7
7
1 stale
2
2
3
1
2
1
1
1
1
47 docs, listed Oct 2
dromara/Sa-TokenOpen repository

Names these docs write that the code no longer has1

Each sentence below names a type the default branch doesn't declare, or declares somewhere else. Edit the doc so it matches the code, or bring the type back.

  • Gonecn.dev33.satoken.dao.SaSessionForJacksonCustomized
    "@class": "cn.dev33.satoken.dao.SaSessionForJacksonCustomized", // java calss 信息

    cn.dev33.satoken.dao declares nothing by this name.

    View on GitHub

dromara/Sa-Token — documented rules

7 of 7 rules, printed October 3, 2026.

The sentence in your docs
Read Oct 2
SaTokenContext只是一个接口,没有工作能力,这也就意味着 SaTokenContext 接口的实现是必须的。 那么疑问来了,我们之前在 SpringBoot 中引用 Sa-Token 时为什么可以直接使用呢?
SaTokenContext is a contract
Holds
Read Oct 2
其实原理很简单,sa-token-spring-boot-starter集成包中已经内置了SaTokenContext的实现:[SaTokenContextForSpring](https://gitee.com/dromara/sa-token/blob/master/sa-token-starter/sa-token-spring-boot-starter/src/main/java/cn/dev33/satoken/spring/SaTokenContextForSpring.java), 并且根据 Spring 的自动注入特性,在项目启动时注入到 Sa-Token 中,做到“开箱即用”。
SaTokenContextForSpring implements SaTokenContext
Holds
Read Oct 2
"Sa-Token 全局类与方法:SaManager 管理配置、Dao、StpLogic 等组件;SaHolder 取当前 Request、Storage;SaRouter 路由鉴权;SaFoxUtil 提供内部工具。另含配置工厂、SpringMVCUtil 与 Reactor Holder,以及事件中心与参数签名入口。"
SaManager depends on StpLogic
Holds
Read Oct 2
不进入是正常现象, StpInterface 是鉴权接口,在执行鉴权代码时才会进入 StpInterface 实现类,登录认证时不会进入。
StpInterface is a contract
Holds
Read Oct 2
在 sa-token-core 核心包中,Sa-Token 底层不能确认最终运行的 web 容器,所以抽象了 SaTokenContext 接口,对接不同容器时需要注入不同的实现, 通常这个注入工作都是框架自动完成的,你只需要按照文档开始部分集成相应的依赖即可。例如:
SaTokenContext is a contract
Holds
Read Oct 2
<!-- 1、自定义数据加载器:新建 SaOAuth2DataLoaderImpl 实现 SaOAuth2DataLoader 接口。
SaOAuth2DataLoaderImpl implements SaOAuth2DataLoader
Holds
Read Oct 2
前面几篇介绍的api调用,都是经过 StpUtil 类的各种静态方法进行授权认证, 而如果我们深入它的源码,[点此阅览](https://gitee.com/dromara/sa-token/blob/master/sa-token-core/src/main/java/cn/dev33/satoken/stp/StpUtil.java) <br/> 就会发现,此类并没有任何代码逻辑,唯一做的事就是对成员变量stpLogic的各个API包装一下进行转发。
StpUtil depends on StpLogic
Holds
7 rules from 5 docs

See these where the change is. The browser extension puts a pull request's doc findings, and a diagram of what it changed, on the GitHub page itself, so the code and what your docs say about it are side by side.