decodeJwtExpiryEpochSeconds — @gj-kit/expo-auth
@gj-kit/expo-auth에서 공개하는 function입니다. package version 0.1.1의 release declaration을 그대로 표시합니다.
검증된 import 예제
섹션 제목: “검증된 import 예제”import { decodeJwtExpiryEpochSeconds } from '@gj-kit/expo-auth';시그니처, 매개변수, 반환 타입
섹션 제목: “시그니처, 매개변수, 반환 타입”/** * ⚠ **This is a payload decode WITHOUT signature verification.** It base64url-decodes the * payload and reads the `exp` claim; it guarantees nothing about the token's authenticity or * integrity. It exists solely as a proactive-refresh scheduling hint — never use it for * authorization decisions or as a trust boundary. The worst a forged `exp` can cause is a * mistimed refresh, and the reactive 401 path is the safety net for that (§7-1). * * Corrupt or non-JWT input returns `null` without throwing (H13). */declare function decodeJwtExpiryEpochSeconds(token: string): number | null;이 선언은 매개변수, optionality, 제네릭, 반환값, 공개 union/type 계약의 정본입니다. 호출 전 필요한 환경·권한·오류 경계는 패키지 Golden path와 이 subpath의 import 조건을 함께 확인하세요.
Release context
섹션 제목: “Release context”- 패키지:
@gj-kit/expo-auth - 버전:
0.1.1 - 공개 entry:
. - 소스: GitHub
구현 주석
섹션 제목: “구현 주석”⚠ This is a payload decode WITHOUT signature verification. It base64url-decodes the
payload and reads the exp claim; it guarantees nothing about the token’s authenticity or
integrity. It exists solely as a proactive-refresh scheduling hint — never use it for
authorization decisions or as a trust boundary. The worst a forged exp can cause is a
mistimed refresh, and the reactive 401 path is the safety net for that (§7-1).
Corrupt or non-JWT input returns null without throwing (H13).