Skip to content

[Frontend] Self-host the Leaflet marker icons instead of loading them from third-party CDNs #1441

Closed

Description

@BigBen-7

Found in a repository audit of main (b472e6b). The facts below were checked against that commit.

Problem

Map.tsx loads marker images at runtime from raw.githubusercontent.com/pointhi/leaflet-color-markers and the shadow from cdnjs.cloudflare.com/ajax/libs/leaflet/0.7.7 (an old Leaflet release). The map breaks if either host is slow or blocked, leaks user IPs to third parties, and complicates any future Content-Security-Policy.

Fix

Vendor the icons into public/ (or use Leaflet's bundled ones) and reference them locally.

Acceptance criteria

  • No third-party image URLs remain in Map.tsx
  • Markers render offline with the dev server

Notes

Scope: Light (about half a day or less). Location: Frontend/src/components/map/Map.tsx.

Activity

  1. ravimahatonp commented on Oct 14, 2026

    @ravimahatonp

    Hello team,

    I examined the issue "[Frontend] Self-host the Leaflet marker icons instead of loading them from third-party CDNs" in PinSpace-Org/GistPin and would be glad to implement the required changes.

    Technical Implementation Outline:

    1. Audit component lifecycle, state synchronization, and reactive props.
    2. Implement clean responsive layout with TypeScript typings and proper accessibility.
    3. Add automated component unit tests covering loading, empty, and error states.
    4. Verify clean production build without console warnings or lint errors.

    Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!

  2. portableDD commented on Oct 17, 2026

    @portableDD
    Contributor

    @portableDD has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi there, I'd like to contribute to this.

    I'm a software engineer with strong experience in JavaScript and building scalable web applications. I'm comfortable working across the stack, writing clean, maintainable code, and collaborating in open source environments.

    I've gone through the details of this issue and I'm confident I can deliver a clean, well-tested solution that fits the codebase.

    I'd love the opportunity to work on this — please consider assigning it to me.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @portableDD to this issue.

  3. drips-wave commented on Oct 17, 2026

    @drips-wave

    Congratulations, @portableDD! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @portableDD: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  4. grantfox-oss commented on Oct 17, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @portableDD's PR #1523 was approved and merged by @BigBen-7.

    🏆 @portableDD: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,388 total points). Track your full progress on GrantFox.

    👏 Great work, @portableDD! Keep contributing to PinSpace-Org.

  5. drips-wave commented on Oct 17, 2026

    @drips-wave

    This issue has been completed by @portableDD as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @portableDD: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programfrontendFrontend (Next.js) issuessecuritySecurity configs

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions