Back to time 0.3.49
Review rev_dbe6a7f890a04e368edadf56dc6ed2b9
UserOfficiald7d85a95-49ea-818b-aa46-7dff97fe9263
Review Details
Package
time@0.3.49
Registry
crates.io
Package Hash
Files Reviewed
5
Agent
codex-gpt-5.4-mini-high
Review Procedure
file-focused-review/v1
Created
2026-07-14
Severity
noneConfidence
high{
"review_procedure": "file-focused-review/v1",
"public_user_id": "d7d85a95-49ea-818b-aa46-7dff97fe9263",
"agent": {
"name": "codex",
"model": "gpt-5.4-mini",
"reasoning_effort": "high"
},
"files": [
{
"path": "src/weekday.rs",
"hash": "blake3:f1dad4b0416f7e891495f29ccccfa8fec434ba7b04596e7d55dc2871f909192e",
"summary": "Reviewed `src/weekday.rs`, which defines the `Weekday` enum plus arithmetic, display, and string-parsing helpers. I found no concrete indicators of install-time execution, network or exfiltration behavior, credential access, dynamic code loading, obfuscation, persistence, or other supply-chain compromise patterns in this file.",
"severity": "none",
"confidence": "high"
},
{
"path": "tests/integration/compile-fail/invalid_date.rs",
"hash": "blake3:fada9e44e74e88ed27257345565067575032826944a0c48ac6dc2237fe93e040",
"summary": "Reviewed `tests/integration/compile-fail/invalid_date.rs`, which is a compile-fail test exercising the `time::macros::date` macro with malformed date literals to verify parser rejection. I found no concrete malicious or supply-chain indicators in this file: no install hooks, network/exfiltration, credential access, dynamic code loading, obfuscation, or persistence behavior.",
"severity": "none",
"confidence": "high"
},
{
"path": "tests/integration/compile-fail/invalid_datetime.rs",
"hash": "blake3:f87523b9dc63890383d839b26257f9ae02dedaf92666762157038c84624cbb7a",
"summary": "Reviewed `tests/integration/compile-fail/invalid_datetime.rs`, which is a small compile-fail test that exercises the `time::macros::datetime` macro with invalid literals to verify parser errors. I checked for install-time execution, network or exfiltration behavior, credential access, dynamic code loading, obfuscation, and persistence mechanisms, and found no concrete malicious or supply-chain indicators in this file.",
"severity": "none",
"confidence": "high"
},
{
"path": "tests/integration/compile-fail/invalid_format_description.rs",
"hash": "blake3:c0a7be81e338d3167820c8526786a6b9d7e3ee85bfebcb3cbc18fa31d2160f8e",
"summary": "`tests/integration/compile-fail/invalid_format_description.rs` is a compile-fail test that feeds malformed format-description inputs to `time::macros::format_description!` to verify parser diagnostics. I checked it for install-time execution, network or exfiltration, credential access, dynamic code loading, obfuscation, persistence, and hidden subprocess behavior, and found no concrete malicious or supply-chain indicators.",
"severity": "none",
"confidence": "high"
},
{
"path": "tests/integration/compile-fail/invalid_offset.rs",
"hash": "blake3:75203f583126857cc4f835e0da94aa117d40db322a04bb2760e1f8611ab87f84",
"summary": "Reviewed `tests/integration/compile-fail/invalid_offset.rs`, which is a compile-fail test exercising `time::macros::offset` with invalid offset literals. I found no concrete indicators of install hooks, network or exfiltration behavior, credential access, dynamic code loading, obfuscation, persistence, or other supply-chain abuse in this file.",
"severity": "none",
"confidence": "high"
}
]
}