Enter your ZIP to see whether this is legal to plant in your state, and whether it survives your winter.
Elaeagnus pungens presents a conflict, and the evidence table retains the cited directions rather than choosing one on the reader's behalf.
Irrigated is the recorded condition in test conditions. The record also carries 1 ecological invasive report as separate status context, keeping that report outside the fire-evidence tally.
Same-form alternatives appear under related plants. They support comparison after the conflict has been read; they do not replace the cited result or turn the ecological report into fire evidence. Each selected fact therefore remains visible at its own destination. That boundary matters when sources disagree.
Marin County (CA footprint); partial normalized coverage · 2019-01-01
The publication is explicitly limited to plants common to Marin County. FireApproved publishes 104 exact owners as Marin regional context while retaining its placement, spacing, irrigation, and maintenance boundary. It is not statewide California guidance or parcel suitability.
Sun City Texas, Georgetown (TX footprint); partial normalized coverage · 2015-01-14
The guide is authored for the Sun City Texas community in Georgetown. FireApproved publishes 142 exact owners only as community-level context. It is an archived HOA exhibit with unknown rating lineage, not a current statewide Texas source or an independent Tier 1 determination.
Travis County, Austin area (TX footprint); partial normalized coverage · 2024-01-16
Texas A&M AgriLife Extension publishes this page through its Travis County horticulture program. FireApproved publishes 56 exact owners and retains the source's zone and warning conditions. This is county/Austin regional context, not a second statewide Texas table or site clearance.
Virginia Cooperative Extension's publication opens with Virginia wildfire conditions, identifies its Virginia Firewise Landscaping Task Force, and labels plants native to Virginia. FireApproved publishes 306 exact source owners. Publication scope does not establish parcel suitability or current endorsement of this archived 2009 list.
2. Why this plant is relevant here
State distribution
Documented in AL, DC, DE, FL, GA, KY, LA, MA, MD, MS, NC, NJ, OH, PA, SC, TN, TX, VA, WV.
Native range
Introduced / established
16 sourced range or established records. This is not an invasive warning.
USDA hardiness
Only uncertain or inapplicable hardiness rows are cited; no primary zone is projected.
3. Legal, ecological, and broader status
Legal-list status
Seed-list status
Reported invasive here
1 ecological invasive report.
Broader regional context
Federal context
How to read this page
The status above is computed from the cited rows below: independent recommendations can support a fire-resistant result, an avoid row can produce keep-away, and disagreement stays visible as conflict. Placement notes preserve each source’s own scheme rather than translating unlike rules into one scale. This is evidence about a plant, not permission to plant it in every part of the defensible space; Zone 0 remains noncombustible.
Native and introduced range evidence
These are exact U.S. botanical-area records from the cited range source. Native and
introduced describe biogeographic relationship, not fire performance or planting approval.
Doubtful and extinct rows stay visible but do not count as current presence.
The lossless worldwide derivative is retained once in the research corpus; object pages repeat only exact U.S. areas needed by the local lens. The JSON twin carries the same page assertions.
Plant hardiness evidence
These values describe the plant source. Your ZIP zone comes from the separate 2023 USDA
Plant Hardiness Zone Map. Whole-zone values stay whole-zone, and a single unresolved value
is not treated as a tolerance range. Different source boundaries stay separate: overlapping
statements are compared independently, while only ranges with no shared zone are called a conflict.
Source prints 7 · single-value meaning unresolved · whole zone precision · source stated
Source taxon: Elaeagnus pungens · exact match.
Source location: Cold Hardiness Zone field in the recovered selector record.
Not used for comparison: The recovered selector prints one Cold Hardiness Zone value but does not define it as a minimum threshold or a one-zone range.
Conditions in the fire evidence
These describe tested or rated plant material. They are not horticultural maintenance instructions.
Placement rules below use each source's own distances or named zones, tied to its rating.
They are not interchangeable with the directory's current Zone 0 guidance.
Eastern United States Fire Performance Plant Selector: Landscape Zone 3 — 10–30 ft from the structure; thin vegetation, remove debris, and minimize plant massing [Fire Performance Plant Selector landscape zone] (with its avoid rating)
Firewise Landscaping: Small Shrubs [Travis County Firewise page sections] (with its avoid rating)
Firewise Plant Guide: Small Trees [Sun City plant-table sections] (mid-scale rating)
The evidence
Grouped by what each source concluded. Primary evidence rated the plant itself
(a lab, field program, or original curation); corroboration compiled or
republished another source's rating and resolves to its root lineage.
“Plants to Avoid for Zone 1 (within 30′ of Structure)”
Listed as Elaeagnus — Elaeagnus pungens. The page says Zone 1 entries should be restricted to zones 2 or 3; all-zone entries are highly flammable due to volatile oils or growth habit.
The table rates Silverthorn, thorny elaeagnus — Elaeagnus pungens medium for flammability hazard, defined as the ease a plant can burn at high temperatures for a prolonged time.
