fix: update contact email to [email protected] across multiple documents

.github/README.md

@@ -323,7 +323,7 @@ Add WeChat for further consults is also an option:
 
 Our QQ Group: 832039395
 
-Mailbox: opensca@anpro-tech.com
+Mailbox: opensca@xmirror.cn
 
 ## Authors
 

CONTRIBUTING-zh_CN.md

@@ -40,11 +40,11 @@ OpenSCA社区尚处于起步阶段，由悬镜安全OpenSCA项目团队管理。
 
 ### 如何提出BUG
 
-如果您在部署或使用OpenSCA时发现了BUG，可以在Issue板块提出；如果您对我们已经上传的公开文档中的内容有疑惑，可以直接发送邮件到 [[email protected]](mailto:[email protected])，也可通过OpenSCA社区微信公众号、微信群、QQ群等渠道联系我们。
+如果您在部署或使用OpenSCA时发现了BUG，可以在Issue板块提出；如果您对我们已经上传的公开文档中的内容有疑惑，可以直接发送邮件到 [[email protected]](mailto:[email protected])，也可通过OpenSCA社区微信公众号、微信群、QQ群等渠道联系我们。
 
 在提出BUG之前，您需要先确认您部署的是OpenSCA的最新版本，然后浏览Issue板块，确认该BUG没有被其他人提出过。以上步骤确认无误后，您可以在Issue板块提出您发现的BUG，等待项目成员或其他社区成员参与讨论或进行处理；也可以提一个PR对它进行修复，然后等待项目成员的审核。
 
-*漏洞问题不适合公开提出或进行讨论，如果您发现了OpenSCA的安全漏洞，请发送相关信息到[[email protected]](mailto:[email protected])与我们取得联系。
+*漏洞问题不适合公开提出或进行讨论，如果您发现了OpenSCA的安全漏洞，请发送相关信息到[[email protected]](mailto:[email protected])与我们取得联系。
 
 ### BUG类型划分
 

CONTRIBUTING.md

@@ -36,7 +36,7 @@ The emerging community is now run by OpenSCA project team. As the development of
 
 The current contributing system can be roughly divided into two parts: one about code and the other about points. For the code branch, you will become a contributor after contributing code through **Pull Request**s and getting accepted by the team. Then you'll be able to participate in the further plan and implementation for the project, judgment for the BUG, review the PR and verify new contributors.
 
-For the points branch, apart from gaining them through contributing code, it also works to actively get involved in reporting BUG, discussing relevant technology and sharing your experience of using OpenSCA. The points could exchange for gifts. The detailed rules of gaining and exchanging points could differ according to time or diverse activities. Please feel free to throw an email to [email protected] for the latest rules. 
+For the points branch, apart from gaining them through contributing code, it also works to actively get involved in reporting BUG, discussing relevant technology and sharing your experience of using OpenSCA. The points could exchange for gifts. The detailed rules of gaining and exchanging points could differ according to time or diverse activities. Please feel free to throw an email to [email protected] for the latest rules. 
 
 ### Report a BUG
 

README.md

@@ -338,7 +338,7 @@ v1.0.5及更低版本需要自行修改源码配置镜像库地址，建议升
 
 QQ技术交流群：832039395
 
-官方邮箱：<opensca@anpro-tech.com>
+官方邮箱：<opensca@xmirror.cn>
 
 ## 贡献者
 

SECURITY.md

@@ -1,6 +1,6 @@
 # Reporting security issue
 
-If you think you have found a security vulnerability, please send a report to [opensca@anpro-tech.com](mailto:opensca@anpro-tech.com). This address can be used for all of OpenSCA Community products (including but not limited to OpenSCA-cli, OpenSCA-IntelliJ-Plugins, OpenSCA-VSCode-Plugins and opensca.xmirror.cn) We Can accept only vulnerability reports at this address.
+If you think you have found a security vulnerability, please send a report to [opensca@xmirror.cn](mailto:opensca@xmirror.cn). This address can be used for all of OpenSCA Community products (including but not limited to OpenSCA-cli, OpenSCA-IntelliJ-Plugins, OpenSCA-VSCode-Plugins and opensca.xmirror.cn) We Can accept only vulnerability reports at this address.
 
 OpenSCA Community will send you a response indicating the next steps in handing your report. After the initial reply to your report, the security team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
 

docker/Dockerfile

@@ -15,7 +15,7 @@ RUN CGO_ENABLED=0 GOOS=linux \
     -o /app/opensca-cli main.go
 
 FROM ${BASEIMAGE}
-LABEL authors="OpenSCA Team <opensca@anpro-tech.com>"
+LABEL authors="OpenSCA Team <opensca@xmirror.cn>"
 
 COPY --from=builder /app/opensca-cli /app/opensca-cli
 COPY --from=builder /app/config.json /app/config.json

docs/Contributing_Guideline-v1.0-zh_CN.md

@@ -38,11 +38,11 @@ OpenSCA社区尚处于起步阶段，由悬镜安全OpenSCA项目团队管理。
 
 ### 如何提出BUG
 
-如果您在部署或使用OpenSCA时发现了BUG，可以在Issue板块提出；如果您对我们已经上传的公开文档中的内容有疑惑，可以直接发送邮件到 [[email protected]](mailto:[email protected])，也可通过OpenSCA社区微信公众号、微信群、QQ群等渠道联系我们。
+如果您在部署或使用OpenSCA时发现了BUG，可以在Issue板块提出；如果您对我们已经上传的公开文档中的内容有疑惑，可以直接发送邮件到 [[email protected]](mailto:[email protected])，也可通过OpenSCA社区微信公众号、微信群、QQ群等渠道联系我们。
 
 在提出BUG之前，您需要先确认您部署的是OpenSCA的最新版本，然后浏览Issue板块，确认该BUG没有被其他人提出过。以上步骤确认无误后，您可以在Issue板块提出您发现的BUG，等待项目成员或其他社区成员参与讨论或进行处理；也可以提一个PR对它进行修复，然后等待项目成员的审核。
 
-*漏洞问题不适合公开提出或进行讨论，如果您发现了OpenSCA的安全漏洞，请发送相关信息到[[email protected]](mailto:[email protected])与我们取得联系。
+*漏洞问题不适合公开提出或进行讨论，如果您发现了OpenSCA的安全漏洞，请发送相关信息到[[email protected]](mailto:[email protected])与我们取得联系。
 
 ### BUG类型划分
 

docs/Contributing_Guideline-v1.0.md

@@ -34,7 +34,7 @@ The emerging community is now run by OpenSCA project team. As the development of
 
 The current contributing system can be roughly divided into two parts: one about code and the other about points. For the code branch, you will become a contributor after contributing code through **Pull Request**s and getting accepted by the team. Then you'll be able to participate in the further plan and implementation for the project, judgment for the BUG, review the PR and verify new contributors.
 
-For the points branch, apart from gaining them through contributing code, it also works to actively get involved in reporting BUG, discussing relevant technology and sharing your experience of using OpenSCA. The points could exchange for gifts. The detailed rules of gaining and exchanging points could differ according to time or diverse activities. Please feel free to throw an email to [email protected] for the latest rules. 
+For the points branch, apart from gaining them through contributing code, it also works to actively get involved in reporting BUG, discussing relevant technology and sharing your experience of using OpenSCA. The points could exchange for gifts. The detailed rules of gaining and exchanging points could differ according to time or diverse activities. Please feel free to throw an email to [[email protected]](mailto:[email protected]) for the latest rules.
 
 ### Report a BUG