This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.

Crate cargo-generate

Dependencies

(35 total, 6 outdated, 2 possibly insecure)

CrateRequiredLatestStatus
 git2~0.20.40.20.4up to date
 anstyle~1.01.0.14up to date
 anyhow~1.01.0.102up to date
 auth-git2~0.50.5.8up to date
 clap~4.5.544.6.0out of date
 console~0.160.16.3up to date
 dialoguer~0.120.12.0up to date
 env_logger~0.110.11.10up to date
 fs-err~3.23.3.0out of date
 gix-config~0.480.54.0out of date
 heck~0.50.5.0up to date
 home~0.50.5.12up to date
 ignore~0.40.4.25up to date
 indexmap~22.13.0up to date
 indicatif~0.180.18.4up to date
 liquid~0.260.26.11up to date
 liquid-core~0.260.26.11up to date
 liquid-derive~0.260.26.10up to date
 liquid-lib~0.260.26.11up to date
 log~0.40.4.29up to date
 names~0.140.14.0up to date
 openssl ⚠️~0.100.10.76maybe insecure
 pastey~0.20.2.1up to date
 regex~1.121.12.3up to date
 remove_dir_all~1.01.0.0up to date
 rhai~1.231.24.0out of date
 sanitize-filename~0.60.6.0up to date
 semver~1.01.0.27up to date
 serde~1.01.0.228up to date
 tempfile^3.24.03.27.0up to date
 thiserror~2.02.0.18up to date
 time ⚠️~0.30.3.47maybe insecure
 toml~0.91.1.1+spec-1.1.0out of date
 walkdir~2.52.5.0up to date
 cargo-util-schemas~0.10.20.12.0out of date

Dev dependencies

(5 total, 1 outdated)

CrateRequiredLatestStatus
 assert_cmd~2.12.2.0out of date
 bstr~1.121.12.1up to date
 indoc~2.02.0.7up to date
 predicates~3.13.1.4up to date
 url~2.52.5.8up to date

Security Vulnerabilities

openssl: Use-After-Free in `Md::fetch` and `Cipher::fetch`

RUSTSEC-2025-0022

When a Some(...) value was passed to the properties argument of either of these functions, a use-after-free would result.

In practice this would nearly always result in OpenSSL treating the properties as an empty string (due to CString::drop's behavior).

The maintainers thank quitbug for reporting this vulnerability to us.

time: Denial of Service via Stack Exhaustion

RUSTSEC-2026-0009

Impact

When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario.

Patches

A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack.

Workarounds

Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input.