Epic: v1.0 stable platform
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 技术栈
- typescript
调研方向
This is a tracking issue rather than a scoped code change; no files or tests are named. Start by reviewing the linked contract, error-shape, and per-flow issues, then clarify with maintainers which open milestone is actionable. Done would require completing an agreed milestone; the licensing item is already resolved by #335.
由索引模型根据 Issue 内容生成。
描述
v1.0 release epic
This issue is the epic for the v1.0 milestone: a stable platform people can bet on. Besides the items below it covers an upgrade and version-skew policy, config as code, full export, an independent security review, a reference deployment, and the run-anywhere items (#374 to #377). All are linked as sub-issues.
Context
From a project-quality review. The engineering fundamentals are strong (correct token rotation + reuse detection, constant-time comparisons, RS256 pinned, fail-closed secrets, broad test coverage). The gaps to a broad "yes, use this in production" recommendation are about project maturity, not code quality. This is a tracking issue for those.
Milestones
- Stable, documented contract + 1.0. Freeze route/schema/token/status-code contract; finish in-flight deprecations (e.g.
GET /logout). Ties into the error-shape and per-flow contract issues. - Independent security audit / pentest you can cite, focused on the auth, token, OTP, session, and crypto paths.
- Reduce bus factor — a second maintainer or an org/sponsor backing, so CVE response does not depend on one person.
- Licensing path for AGPL-averse adopters — evaluate a dual-license / commercial option so the AGPL-3.0 terms are not a hard blocker for companies. Decided 2026-10-05: relicense the whole ecosystem to Apache-2.0 instead of a dual license (#335). Done: everything is Apache-2.0 as of #335.
- Reference production deployment(s) / case study to demonstrate real-world operation.
Why it matters
For an auth server, longevity, audit attestation, and maintainer responsiveness weigh as heavily as code quality for adopters in regulated or high-stakes contexts.
- 主要语言
- TypeScript
- 星标
- 2
- 派生
- 2
- 平均合并
- 11 小时 40 分钟
- 30 天内合并 PR
- 104
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
fells-code/seamless-auth-api 的其他 Issue
-
easy P2 v0.23
难度 4/5 一周以上 新手友好度 8/100
fells-code/seamless-auth-api#561 ·
维护者通常 1 天内回复
-
epic P1 security v0.23
难度 5/5 一周以上 新手友好度 8/100
fells-code/seamless-auth-api#558 ·
维护者通常 1 天内回复
-
P1 security v0.23
难度 3/5 半天 新手友好度 55/100
fells-code/seamless-auth-api#553 ·
维护者通常 1 天内回复
-
epic P2 v0.23
难度 5/5 一周以上 新手友好度 5/100
fells-code/seamless-auth-api#551 ·
维护者通常 1 天内回复
-
P2 secure v2.1
难度 5/5 一周以上 新手友好度 25/100
fells-code/seamless-auth-api#512 ·
维护者通常 1 天内回复
查看 fells-code/seamless-auth-api 的全部 Issue
相似的 Issue
-
desktop v3 windows
难度 2/5 1-3 小时 新手友好度 75/100
esengine/DeepSeek-Reasonix#15016 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
readest/readest#7413 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement good first issue priority: medium size: XS
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
content triage
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
eliasstravik/herdr-projects#788 ·