Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Improve CSP Documentation & Consider Full CSP Compliance in Plotly.js

未關閉
#7,349 2 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@emilykl 已經在處理了。

開始於 2025年1月29日。

評估

這個 Issue 還沒有評估資料。

描述

cs documentation feature P1
Title: Improve CSP Documentation & Consider Full CSP Compliance in Plotly.js
Description

Plotly.js provides a strict CSP bundle for users with strong Content Security Policies (CSP), but clear documentation is missing on:

  • What’s included/excluded in the strict bundle
  • Known limitations and workarounds

Enterprise customers and community users (e.g., this forum post) have requested better CSP support and clarity. The strict bundle exists (plotly-strict.js), but its usage is not well-documented.


Proposed Actions
  1. Document the strict bundle’s capabilities, limitations, and integration steps.
  2. Provide examples for CSP-compliant usage in Dash & JS.
  3. Evaluate full CSP compliance for Plotly.js instead of maintaining a separate bundle.
    • Internal enterprise customers have requested a fully CSP-compliant version.
    • Can the main plotly.js bundle be refactored to remove eval and inline scripts?

Why This Matters
  • CSP restrictions block adoption in security-sensitive environments.
  • Clear documentation would prevent confusion and production roadblocks.
  • Growing demand from enterprises & community users for strict CSP support.

Can the team consider making the main bundle fully CSP-compliant? Are there technical challenges or funding requirements for this? 🚀

主要語言
JavaScript
星號
18.4k
分支
2k
平均合併
2 天 5 小時
30 天內合併 PR
16

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

plotly/plotly.js 的其他 Issue

查看 plotly/plotly.js 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。