arkanalyzer 1.0.5

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.en.md

@@ -0,0 +1,88 @@
+# sig_programanalysis
+
+English | [简体中文](./README.md)
+
+## SIG Group Work Objectives and Scope
+
+### Work Objectives
+
+* Sig_programanalysis aims to carry out program analysis technology exploration, key technology identification, and competitiveness building for OpenHarmony systems and apps, striving to become the gathering place for OpenHarmony system and app analysis capabilities and an incubation place for related engineering tools.
+
+* Sig_programanalysis will build a basic program analysis framework for OpenHarmony apps, and subsequently based on it to provide application developers with out-of-the-box defect scanning and analysis tools, making it possible to automatically vet code for scenarios such as IDE, CI/CD pipelines, etc.
+
+### Work Scope
+
+* Responsible for building and maintaining the key technology map of program analysis, as well as the decomposition of functional modules in the field, interface definition, and maintenance management.
+
+* Responsible for the architecture design, open source development, and project maintenance of projects related to program analysis.
+
+
+### Projects
+
+Sig_programanalysis currently incubates the following projects. Everyone is welcome to participate (you can apply to participate in the co-construction of existing projects, or you can apply to create a new program analysis project).
+
+
+* ArkAnalyzer:
+The Static Analysis Framework for ArkTS-based OpenHarmony Apps.
+
+* ArkCheck:
+Checking OpenHarmony Apps for Potential Code-level Defects
+
+
+## SIG Members
+
+
+### Leader
+
+- [lilicoding](https://gitee.com/lilicoding)
+
+
+### Committers
+- [kubigao](https://gitee.com/kubigao)
+- [yifei-xue](https://gitee.com/yifei_xue)
+- [kubrick-hjh](https://gitee.com/kubrick-hjh)
+- [speed9](https://gitee.com/speeds)
+- [bbsun](https://gitee.com/bbsun)
+- [chn](https://gitee.com/chn)
+- [Elouan](https://gitee.com/Elouan)
+- [Rnine](https://gitee.com/Rnine)
+- [workspace_cb](https://gitee.com/workspace_cb)
+- [longyuC](https://gitee.com/longyuC)
+- [xyji95](https://gitee.com/xyji95)
+- [xulingyun-red](https://gitee.com/xulingyun-red)
+
+
+### Meetings
+ - Meeting Time: Bi-weekly meeting, Thursday 19:30 Beijing time
+ - Meeting Application：[Link](https://shimo.im/forms/B1Awd60W7bU51g3m/fill)
+ - Meeting Link: Welink or Others
+ - Meeting Notification: [Subscribe to](https://lists.openatom.io/postorius/lists/dev.openharmony.io) mailing list dev@openharmony.io for the meeting link
+ - Meeting Summary: [Archive link address](https://gitee.com/openharmony-sig/sig-content)
+
+### Contact
+
+- Mailing list: [dev@openharmony.io](https://lists.openatom.io/postorius/lists/dev@openharmony.io/)
+
+*** 
+# ArkAnalyzer: Static Program Analysis Framework for the ArkTS Language
+## Develope environment setup
+1. [Download Visual Studio Code](https://code.visualstudio.com/download) or other IDEA;
+2. [Download Node.js](https://nodejs.org/en/download/current) and install it. Node.js is a runtime environment for JavaScript, which comes with its own package manager, npm. 
+3. Install Typescript via npm: 
+```shell
+npm install -g typescript
+```
+4. Install dependency libraries
+```shell
+cd arkanalyzer
+npm install
+```
+
+## Commit codes
+Follow the code repository standards of Openharmony-Sig, refer to the [link](docs/HowToCreatePR.md#english)
+
+## Debug
+Modify the `args` parameter array in the debug configuration file `.vscode/launch.json` to the path of the test file you want to debug, and then start the debugging process.
+
+## Add test cases
+Place all new test codes in the `tests` directory. Corresponding sample code and other resource files should be placed in the ``tests\resources` directory, and create different folders for each testing scenario.

package/README.md

@@ -0,0 +1,98 @@
+# sig_programanalysis
+
+简体中文 | [English](./README.en.md)
+
+说明：本SIG的内容遵循OpenHarmony的PMC管理章程 [README](../../zh/pmc.md)中描述的约定。
+
+
+## SIG组工作目标和范围
+
+  
+
+### 工作目标
+
+* 程序分析-SIG（Sig_programanalysis） 旨在面向OpenHarmony系统和原生应用开展程序分析技术洞察、关键技术识别和竞争力构建，同时成为OpenHarmony系统和应用程序分析能力的聚集地和相关工程工具的孵化地。
+
+* 程序分析-SIG（Sig_programanalysis）将面向OpenHarmony应用构建基础程序分析框架并基于此为应用开发者提供开箱即用的缺陷扫描分析工具，面向IDE、流水线门禁、应用市场上架审核等场景，打造自动化工具看护能力。
+
+### 工作范围
+
+* 负责程序分析子领域关键根技术地图梳理，以及领域内功能模块分解、接口定义与维护管理等工作。
+
+* 负责程序分析子领域相关项目的架构设计、开源开发和项目维护等工作。
+
+
+### 项目孵化
+
+程序分析-SIG（Sig_programanalysis）正积极孵化如下项目，欢迎大家参与共享共建（可申请参与已有项目的共建，也可申请创建新的程序分析项目并联合社区启动开源共建）。
+
+
+* 方舟分析器（ArkAnalyzer）:
+	面向ArkTS的OpenHarmony应用程序分析框架。
+
+* 方舟检测器（ArkCheck）:
+	面向OpenHarmony应用开发提供代码级缺陷自动检测（I期聚焦高性能编码规则的自动化检测）
+
+
+
+## SIG组成员
+
+
+### Leader
+
+- [lilicoding](https://gitee.com/lilicoding)
+
+
+### Committers列表
+- [kubigao](https://gitee.com/kubigao)
+- [yifei-xue](https://gitee.com/yifei_xue)
+- [kubrick-hjh](https://gitee.com/kubrick-hjh)
+- [speed9](https://gitee.com/speeds)
+- [bbsun](https://gitee.com/bbsun)
+- [chn](https://gitee.com/chn)
+- [Elouan](https://gitee.com/Elouan)
+- [Rnine](https://gitee.com/Rnine)
+- [workspace_cb](https://gitee.com/workspace_cb)
+- [longyuC](https://gitee.com/longyuC)
+- [xyji95](https://gitee.com/xyji95)
+- [xulingyun-red](https://gitee.com/xulingyun-red)
+
+
+### 会议
+ - 会议时间：双周例会，周四晚上19:00, UTC+8
+ - 会议申报：[申报链接](https://shimo.im/forms/B1Awd60W7bU51g3m/fill)
+ - 会议链接：Welink或其他会议
+ - 会议通知：请[订阅](https://lists.openatom.io/postorius/lists/dev.openharmony.io)邮件列表 dev@openharmony.io 获取会议链接
+ - 会议纪要：[归档链接地址](https://gitee.com/openharmony-sig/sig-content)
+
+
+### Contact (optional)
+
+- 邮件列表：[dev@openharmony.io](https://lists.openatom.io/postorius/lists/dev@openharmony.io/)
+
+***
+
+# 方舟分析器：面向ArkTS语言的静态程序分析框架
+## ArkAnalyzer 环境配置
+1. 从[Download Visual Studio Code](https://code.visualstudio.com/download)下载vscode并安装，或安装其他IDE。
+2. 从[Download Node.js](https://nodejs.org/en/download/current)下载Node.js并安装，Node.js为JavaScript的运行时环境，自带包管理器npm。
+3. 通过npm安装TypeScript编译器，命令行输入
+```shell
+npm install -g typescript
+```
+4. 安装依赖库
+```shell
+npm install
+```
+
+## ArkAnalyzer 代码上库
+遵守openharmony-sig代码上库规范, 操作方法请参考：[链接](docs/HowToCreatePR.md#中文)
+
+## ArkAnalyzer 调试
+将调试配置文件`.vscode/launch.json`中`args`参数数组修改为想要调试的文件路径，然后启动调试。
+
+## 添加自验证测试用例
+新增测试代码统一放至`tests`目录下，对应的样例代码和其他资源文件统一放至`tests\resources`,按测试场景创建不同文件夹。
+
+## ArkAnalyzer Issues
+请参考[连接](docs/HowToHandleIssues.md)提交Issues。

package/docs/HowToCreatePR.md

@@ -0,0 +1,55 @@
+# 中文 
+本指导是对[openharmony-sig提交代码规范](https://gitee.com/openharmony-sig/sig-content/blob/master/Infrastructure/docs/manual/gitee%E6%8F%90pr%E5%B8%B8%E8%A7%84%E6%93%8D%E4%BD%9C.md)的扩充
+
+开发者对仓库修改，统一采用向对应仓库提PR的方式来做修改。提PR的方式有两种：
+1. fork工作仓方式：相关的gitee操作请参考此[链接](https://gitee.com/help/articles/4128#article-header0)。
+2. 评审模式：直接向主仓push代码，gitee自动生成PR。相关的操作参考此[链接](https://gitee.com/help/articles/4346)。
+
+以下为一次提交代码的步骤：
+1. **最重要**：提交代码时一定要记得使用git commit -s -m添加signed-off信息，且signed-off中涉及到的邮箱已经在[链接](https://dco.openharmony.io/sign/Z2l0ZWUlMkZvcGVuX2hhcm1vbnk=)中签署DCO
+
+2. 使用`git push origin <分支名>`将指定分支的本地仓库内容推到远端开发者fork仓库（fork工作仓方式）或远端主仓（评审模式）
+
+3. fork工作仓方式：进入远端fork 的仓库，点击新建PR,选择第2步中提交的分支。评审模式：一个PR会自动创建
+
+4. 在主仓新建ISSUE，ISSUE的类型和内容根据提交的代码特性按实际填写
+   
+5. 在PR页面右边栏的“关联ISSUE”选择第4步创建的ISSUE（不关联无法触发门禁）
+   
+6. 在PR页面右边栏选择审查人员
+   
+7. 在评论中输入`start build`，几秒后会触发门禁
+    
+8. 等待门禁后台审核
+
+   * 如果提交的PR显示DCO检查成功，等待管理员审核通过即可，如果DCO检查失败，请确认是否签署DCO。
+
+   * 提交以后，后台会进行自动化的法务合规、cicd的扫描，扫描结果会在提交的PR下以评论的形式展现出来
+
+   * 如果扫描有问题，需要根据反馈进行整改，然后再重新提交，直到审核通过
+  
+9. 门禁全部通过和人员审查通过后，会自动合并代码
+
+***
+# ENGLISH
+This guide is an expansion of the code submission standards of openharmony-sig.
+
+Developers should make modifications to the repository by submitting a PR (Pull Request) to the corresponding repository. There are two ways to submit a PR:
+
+1. Fork repository method: For related Gitee operations, please refer to this [link](https://gitee.com/help/articles/4128#article-header0).
+2. Review mode: Directly push the code to the main repository, and Gitee will automatically generate a PR. For related operations, please refer to this [link](https://gitee.com/help/articles/4346).
+   
+Here are the steps for a code submission:
+
+1. **Most importantly**: When committing code, always remember to use `git commit -s -m` to add signed-off information, and ensure that the email involved in the signed-off has signed the DCO (Developer Certificate of Origin) as [linked](https://dco.openharmony.io/sign/Z2l0ZWUlMkZvcGVuX2hhcm1vbnk=).
+2. Use `git push origin <branch-name>` to push the content of the specified branch in your local repository to the remote developer's forked repository (fork repository method) or to the remote main repository (review mode).
+3. Fork repository method: Enter the remote forked repository and click on "New Pull Request", selecting the branch submitted in step 2. Review mode: A PR will be automatically created.
+4. Create a new ISSUE in the main repository, and fill in the type and content of the ISSUE according to the features of the submitted code.
+5. On the right side of the PR page, under "Associated ISSUE", select the ISSUE created in step 4 (it cannot trigger the gate if not associated).
+6. On the right side of the PR page, select the reviewer.
+7. Enter "start build" in the comments to trigger the gate after a few seconds.
+8. Wait for the gate to be reviewed in the background.
+   * If the submitted PR shows that the DCO check is successful, wait for the administrator to review and pass. If the DCO check fails, please confirm whether you have signed the DCO.
+   * After submission, the background will carry out automated legal compliance and CI/CD scanning, and the results of the scan will be displayed in the form of comments under the submitted PR.
+   * If there are problems with the scan, they need to be rectified according to the feedback and then resubmitted until the review is passed.
+9. After all gates pass and the personnel review is passed, the code will be automatically merged.

package/docs/HowToHandleIssues.md

@@ -0,0 +1,155 @@
+## 1. Issue 分类
+
+所有新提交的 Issue 应该根据其类型进行分类。主要的分类包括：
+
+* Bug
+* 新功能需求
+* 疑问/支持请求
+* 任务
+
+## 2. 初步筛选
+
+当一个新的 Issue 被提交时，项目维护者应执行以下初步筛选步骤：
+
+1. **确认 Issue 描述是否清晰**：确保 Issue 的描述清晰并包含足够的信息。若描述不清晰，向提问者请求更多信息。
+2. **确认 Issue 分类是否正确**：检查 Issue 的分类是否正确，如果不正确，重新分类。
+
+## 3. 处理流程
+
+根据 Issue 的分类，采取不同的处理流程。
+各环节需要补充责任人
+
+### A. Bug
+
+1. **验证 Bug**
+   * 重现问题：尝试重现提到的问题，若为问题，打上标签跟踪。
+   * 收集更多信息：如果需要更多信息（如日志、错误消息、环境配置等），请求提问者提供。
+2. **优先级排序**
+   * 根据 Bug 的严重程度和影响范围，分配优先级。必解问题标为严重，例行跟踪。
+3. **分配处理**
+   * 指派给合适的开发人员进行处理。
+4. **修复 Bug**
+   * 开发人员修复 Bug 并提交 PR。
+5. **测试和关闭**
+   * 测试修复的有效性。
+   * 合并 PR 后关闭 Issue，并通知提问者。
+
+### B. 新功能需求
+
+1. **评估需求**
+   * 讨论需求的可行性和价值，若有价值录入版本需求。
+   * 收集社区和团队的反馈。
+2. **优先级排序**
+   * 根据项目的目标和资源分配优先级。
+3. **分配处理**
+   * 如果决定实施，指派给合适的开发人员进行设计和开发。
+4. **开发新功能**
+   * 开发人员设计、开发并提交 PR。
+5. **测试和发布**
+   * 测试新功能，确保其符合要求。
+   * 合并 PR 并更新文档后关闭 Issue，并通知提问者。
+
+### C. 疑问/支持请求
+
+1. **回应提问**
+   * 及时回应提问，提供解决方案或指导。
+   * 如果问题已在文档中详细说明，提供相关链接。
+2. **解决疑问**
+   * 如果问题复杂，需要进一步讨论和调查，可能需要分配给合适的人员。
+3. **关闭 Issue**
+   * 一旦问题得到解决或指导，关闭 Issue，并通知提问者。
+
+## 4. 通用规范
+
+* **响应时间**：尽量在 48 小时内响应新 Issue。
+* **沟通**：保持透明开放的沟通，确保 Issue 创建者了解 Issue 的处理进展。
+* **文档更新**：根据 Issue 处理过程中的发现和解决方案，及时更新项目文档。
+* **定期检查**：定期检查未关闭的 Issue，确保所有问题都得到适当处理。
+* **审核人**： [xulingyun-red](https://gitee.com/xulingyun-red)、[sfoolish](https://gitee.com/sfoolish)。
+* **标题**：标题可以添加tag方便查看，如[#arkcheckxx]、[#IRRefactorxx]。
+* **标签**：
+  * `Accept`: 审核通过。
+  * `Duplicate`: 重复Issue，注明重复的Issue号，并关闭。
+  * `Reject`: 拒绝Issue，注明拒绝理由（e.g. issue描述不清楚，长期未回复）。
+
+## 5. Milestone管理
+
+* 每月一个里程碑，里程碑名：M-YYYYMM
+* 月度版本需求和必解问题相关Issue标注Milestone和等级
+* 每月10日锁定当月的必交需求和必解问题，10日后的新增问题单独评估是否必解(遇到周末提前锁定)
+* 每月25日初步锁定下个月的必交需求和必解问题，25日后的新增需求单独评估是否必交(遇到周末提前锁定)
+* 加入Milestone的Issue等级：严重(转测前合入) > 主要(转测后可以合入) > 次要(可以遗留) > 不重要(可以遗留)
+
+## 6. 模板和标签
+
+为帮助开发/测试人员提交有效的 Issue，可以使用模板和标签：
+
+### Issue 模板
+
+**1.BUG模版/缺陷**
+
+```
+**【简要描述 / Description】：**
+
+**【测试步骤 / Test procedure】：**
+
+**【预期结果 / Expected result】：**
+
+**【实际结果 / Actual result】：**
+
+**【其它 / Others】：**
+- 1. Log、截图、多媒体文件等，所有和问题有关的信息：
+
+
+e.g.: https://gitee.com/openharmony-sig/arkanalyzer/issues/IAC3AX
+```
+
+**2.需求模版**
+
+```
+**【需求价值 / Value of the Requirement】：**
+
+**【需求描述 / Requirement Description】：**
+
+**【方案描述 / Solution Description】：**
+
+**【配套文档 / Supporting Documentation】：**
+
+**【验收标准 / Acceptance Criteria】：**
+
+e.g.: https://gitee.com/openharmony-sig/arkanalyzer/issues/IACEBC
+```
+
+**3.任务模版**
+
+```
+**【任务描述 / Task Description】：**
+
+**【解决方案 / Solution Description】：**
+
+**【任务来源 / Task Source】：**
+```
+
+## 7. 其它开发过程规范
+
+### A. 分支管理规范
+
+* 所有代码必须先合主干，再合商分。（特性分支除外，特性分支代码开发完后，也需要先回合主干再按需合入商分）
+* gitee与codehub同步创建月度Release分支，Release分支匹配Milestone的需求和必解问题交付。
+* 月度首版本转测后，release分支只合必解问题不合需求，不夹带合入。
+* 底座月度分支合入需要[sfoolish](https://gitee.com/sfoolish)审核，影响对外接口的同时需要[yifei-xue](https://gitee.com/yifei_xue)审核，接口文档需要yanglin审核。
+
+### B. PR提交规范
+
+* 代码合入前先Rebase
+* 代码PR需要刷新，建议通过`git commit --amend` + `git push -f` 刷新，想在主干保留中间状态，建议分多次PR提交
+* 新建的PR提交后都发到review群里
+
+### C. 代码检视 CheckList
+
+1. PR关联的issue已审核且处于open状态。
+2. issue描述、PR描述与代码实际修改保持一致。
+3. 对于一个问题或者需求的提交，不能夹带其它问题或需求的修改。
+4. 门禁问题和检视意见必须全部处理完毕。
+5. 代码保持一定比例的注释，确保在充分理解代码修改的情况下对代码进行检视和合入。
+6. bugfix类PR默认要补充UT用例。

package/lib/Config.d.ts

@@ -0,0 +1,26 @@
+export interface Sdk {
+    name: string;
+    path: string;
+    moduleName: string;
+}
+export declare class SceneConfig {
+    private targetProjectName;
+    private targetProjectDirectory;
+    private etsSdkPath;
+    private sdksObj;
+    private sdkFiles;
+    private sdkFilesMap;
+    private projectFiles;
+    constructor();
+    buildConfig(targetProjectName: string, targetProjectDirectory: string, sdks: Sdk[], fullFilePath?: string[]): void;
+    buildFromProjectDir(targetProjectDirectory: string): void;
+    buildFromJson(configJsonPath: string): void;
+    getTargetProjectName(): string;
+    getTargetProjectDirectory(): string;
+    getProjectFiles(): string[];
+    getSdkFiles(): string[];
+    getSdkFilesMap(): Map<string[], string>;
+    getEtsSdkPath(): string;
+    getSdksObj(): Sdk[];
+}
+//# sourceMappingURL=Config.d.ts.map

package/lib/Config.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"Config.d.ts","sourceRoot":"","sources":["../src/Config.ts"],"names":[],"mappings":"AAsBA,MAAM,WAAW,GAAG;IAChB,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,UAAU,EAAE,MAAM,CAAC;CACtB;AAED,qBAAa,WAAW;IACpB,OAAO,CAAC,iBAAiB,CAAc;IACvC,OAAO,CAAC,sBAAsB,CAAc;IAE5C,OAAO,CAAC,UAAU,CAAc;IAChC,OAAO,CAAC,OAAO,CAAa;IAE5B,OAAO,CAAC,QAAQ,CAAgB;IAChC,OAAO,CAAC,WAAW,CAAsD;IAEzE,OAAO,CAAC,YAAY,CAAgB;;IAK7B,WAAW,CACd,iBAAiB,EAAE,MAAM,EACzB,sBAAsB,EAAE,MAAM,EAC9B,IAAI,EAAE,GAAG,EAAE,EACX,YAAY,CAAC,EAAE,MAAM,EAAE;IAUpB,mBAAmB,CAAC,sBAAsB,EAAE,MAAM;IAMlD,aAAa,CAAC,cAAc,EAAE,MAAM;IAuCpC,oBAAoB;IAIpB,yBAAyB;IAIzB,eAAe;IAIf,WAAW;IAIX,cAAc;IAId,aAAa;IAIb,UAAU;CAGpB"}