mapradar 0.5.0

Turn addresses into coordinates and find nearby amenities using Google Maps API
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

# Security Policy

## Threat Model

Mapradar protects API keys and ensures secure RPC communication for location intelligence.

### In Scope

| Threat | Protection |
|--------|------------|
| API Key Leakage | No keys are hardcoded; environment variables required |
| Network Sniffing | HTTPS is used for all Google Maps API requests |

### Out of Scope

- Root/administrator access
- Physical access attacks
- Social engineering

---

## Implementation

| Component | Choice | Rationale |
|-----------|--------|-----------|
| Transport | HTTPS via reqwest | Secures API requests to external providers |
| Storage | In-memory Cache (Moka) | Fast and prevents persistent data leakage |

---

## Known Limitations

1. API keys are sent over HTTPS to Google Maps but reside in memory during execution.

---

## Vulnerability Disclosure

**Email:** emmypresh777@gmail.com

Do not file public issues for security vulnerabilities.

| Stage | Timeline |
|-------|----------|
| Acknowledgment | 24 hours |
| Assessment | 72 hours |
| Fix | Severity-dependent |

---

## Dependencies

| Library | Purpose |
|---------|---------|
| reqwest | HTTP client |

Advisories tracked via `cargo-audit`.