src/api/pkg.ts exports two functions that nothing calls:
startSession (src/api/pkg.ts:62) — POST /v2/request/start
getSessionJwt (src/api/pkg.ts:83) — GET /v2/request/jwt/{token}
Neither is imported anywhere in src/, tests/, or scripts/, and neither is re-exported from src/index.ts, so they are not part of the public API either. The Yivi flow that would have used them (src/signing/yivi.ts, src/yivi/decrypt-session.ts) drives the session through the yivi-core/yivi-client widgets instead and only calls getUSK / getSigningKeysWithJwt.
Treeshaking keeps them out of dist, so this is source-level debt rather than bundle weight — but they still read as live PKG endpoints a maintainer might rely on.
Remove both functions, plus the SessionStartResult type and any imports that become unused as a result. Keep getUSK, getSigningKeysWithJwt, and fetchMPK.
src/api/pkg.tsexports two functions that nothing calls:startSession(src/api/pkg.ts:62) —POST /v2/request/startgetSessionJwt(src/api/pkg.ts:83) —GET /v2/request/jwt/{token}Neither is imported anywhere in
src/,tests/, orscripts/, and neither is re-exported fromsrc/index.ts, so they are not part of the public API either. The Yivi flow that would have used them (src/signing/yivi.ts,src/yivi/decrypt-session.ts) drives the session through the yivi-core/yivi-client widgets instead and only callsgetUSK/getSigningKeysWithJwt.Treeshaking keeps them out of
dist, so this is source-level debt rather than bundle weight — but they still read as live PKG endpoints a maintainer might rely on.Remove both functions, plus the
SessionStartResulttype and any imports that become unused as a result. KeepgetUSK,getSigningKeysWithJwt, andfetchMPK.