@eeacms/volto-cca-policy

中文文档
1.0.56发布于 2026/11/11MITCommonJS近 30 天下载 4151

@eeacms/volto-cca-policy: Volto add-on

原始使用文档
文档目录6 节
  1. Release
  2. How to contribute
  3. Secret Scanning
  4. Copyright and license
  5. Funding
  6. Funding

volto-cca-policy

Releases

Pipeline Lines of Code Coverage Bugs Duplicated Lines (%)

Pipeline Lines of Code Coverage Bugs Duplicated Lines (%)

Climate-ADAPT Frontend Policy

Volto add-on

Release

See RELEASE.md.

How to contribute

See DEVELOP.md.

Secret Scanning

This repository uses the Betterleaks GitHub Action to scan the current repository content on every push and pull request. The scan uses the rules in .gitleaks.toml and uploads a betterleaks-report artifact when a finding is detected.

If the optional SMTP secrets are configured, failed scans also send an email to the last commit committer. The workflow expects these repository or organization secrets:

  • SMTP_URL
  • SMTP_PORT (optional, defaults to 25)
  • SMTP_EMAIL
  • SMTP_PASSWORD (optional if the SMTP server does not require authentication)

Port 465 is sent with direct TLS; other ports use the default SMTP handshake. The email includes a short finding summary from the redacted Betterleaks report, including the redacted matched line from each finding.

There are three common outcomes:

  1. Everything is OK. The Betterleaks / Scan for secrets check is green and no action is needed. Regular references to runtime values are OK, for example:

    const tokenFromCookie = req.universalCookies.get('auth_token');
    
  2. A real secret was found. The check is red and the workflow log asks you to download the betterleaks-report artifact. Open the artifact from the GitHub Actions run and check the reported file, line and rule. Remove the committed value, move it to the proper secret store, and rotate it if it was exposed. A report entry looks like this:

    {
      "RuleID": "secret-literal-assignment",
      "File": "src/config.js",
      "StartLine": 12,
      "Secret": "[REDACTED]"
    }
    
  3. The finding is a false positive. Keep the value only if it is clearly not sensitive, such as a test fixture, placeholder, or public example. Add betterleaks:allow on the same line and include a short explanation in the pull request.

    const testPassword = 'admin'; //betterleaks:allow
    
    password: "admin" #betterleaks:allow
    

Do not add betterleaks:allow to real credentials.

The Initial Owner of the Original Code is European Environment Agency (EEA). All Rights Reserved.

See LICENSE.md for details.

Funding

European Environment Agency (EU) don-template/blob/master/LICENSE.md) for details.

Funding

European Environment Agency (EU)

版本与发布记录

@eeacms/volto-cca-policy 共发布 391 个版本,首次发布于 2022/12/13;过去 12 个月发布了 99 个版本。

版本发布日期距今
1.0.56latest2026/11/112 天前
1.0.552026/11/103 天前
1.0.542026/11/094 天前
1.0.532026/11/067 天前
1.0.522026/11/067 天前
1.0.512026/11/0310 天前

关于 @eeacms/volto-cca-policy 的常见问题

@eeacms/volto-cca-policy 是什么?

@eeacms/volto-cca-policy: Volto add-on

如何安装 @eeacms/volto-cca-policy?

在项目目录运行 npm install @eeacms/volto-cca-policy,或使用 pnpm add / yarn add / bun add。

@eeacms/volto-cca-policy 支持 TypeScript 吗?

该包的 package.json 没有声明类型入口。需要类型提示时,可以在 npm 上查找社区维护的 @types/eeacms__volto-cca-policy 是否存在。

@eeacms/volto-cca-policy 支持 ESM 还是 CommonJS?

以 CommonJS 形式发布,可以直接 require();在 ES Module 项目中也可以用 import 引入(Node.js 会把 module.exports 作为默认导出)。

@eeacms/volto-cca-policy 可以商用吗?

@eeacms/volto-cca-policy 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@eeacms/volto-cca-policy 的下载量有多少?

根据 npm 官方下载统计,@eeacms/volto-cca-policy 在 2026/10/13 – 2026/11/11 这 30 天内被下载 4,151 次,日均约 138 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@eeacms/volto-cca-policy 还在维护吗?

最新版本 1.0.56 发布于 2026/11/11(2 天前);至今共发布 391 个版本,其中过去 12 个月发布了 99 个;首次发布于 2022/12/13。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。