CodeVetter · Repo Unpack · Risk map
iamkun/dayjs
These are source observations and explicitly identified hypotheses, not confirmed vulnerabilities. The inspected runtime paths principally expose parsing and shared extension state; filesystem mutation and release credentials appear in tooling boundaries. Calendar correctness depends on native Date, Intl data, offset bookkeeping, and plugin composition. Existing regression tests constrain some of these behaviors but were not run.
- Input validation differs by mode: core isValid only checks native invalid-Date state, native component construction can normalize overflow, and customParseFormat rejects round-trip mismatches only when strict mode is requested.
- Plugins execute directly with the shared class and factory and can replace methods globally; badMutable intentionally removes clone-before-set behavior, while advancedFormat and duration call APIs supplied by companion plugins.
- Locale data is shared mutable state: instances resolve $L through Ls at call time, and updateLocale changes registry objects. Hypothesis: runtime locale updates can change output from already-created instances and require application-level coordination. (inferred)
- DST overlap resolution starts with the target zone's offset at the current time, and fixOffset documents that the guess selects ambiguous offsets; broader timezone calendar arithmetic is explicitly deferred in the test source.
- Timezone formatting constructs Intl.DateTimeFormat with caller-supplied zone names and caches by zone/name style without a local eviction or exception handler; invalid-date guards do not validate the zone identifier.
- Duration total-unit conversion assumes 365 days per year and one twelfth of that per month, whereas applying a duration to a date performs calendar-unit additions; consumers must distinguish fixed totals from calendar arithmetic.
- Build tooling writes package artifacts and unlinks relocated declarations; ESM paths partly depend on process.env.PWD. Core build and locale.json writes are not awaited, ESM uses async forEach callbacks, and outer catches log errors without explicitly setting a failing exit code.
- The release job inherits secrets, grants repository write and OIDC permissions, exposes GITHUB_TOKEN to release tooling, and installs additional release packages without saving them; it is a privileged boundary triggered by master pushes.