Skip to content

docs: record exact npm cooldown #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
miakh merged 1 commit into from
Aug 29, 2026
Merged

docs: record exact npm cooldown #21

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/plans/public-security-hardening-plan-2026-08-29.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ the attacker's consumer to another tenant's account.
- `@festapp/banksync` is the canonical npm identity. A bootstrap package was
fully unpublished during namespace setup, so npm enforces its documented
24-hour same-name cooldown; publication cannot resume before approximately
2026-08-30 15:43 CEST. No stable npm version or `v0.1.2` tag exists yet.
2026-08-30 15:48:23 CEST. No stable npm version or `v0.1.2` tag exists yet.
- Production has `BACKUP_ENCRYPTION_KEY_V1`; the same restore key is held
independently outside Cloudflare. `EMAIL_AUTHSERV_ID` intentionally remains
unset until accepted/rejected production evidence establishes the trusted
Expand Down