Skip to content

Commit 9d581e5

Browse files
author
Jing Ling
authored
v0.0.1
1 parent 2eda73e commit 9d581e5

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

82 files changed

+129461
-751
lines changed

CHANGES.md

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# Changelog
2+
OneForAll的所有值得注意的更改都将记录在此文件中。
3+
4+
OneForAll的更新日志格式基于[Keep a Changelog](https://keepachangelog.com/zh-CN/1.0.0/)
5+
6+
OneForAll遵守[语义化版本格式](https://semver.org/)
7+
8+
## [Unreleased](https://github.com/shmilylty/onefroall/compare/v1.0.0...HEAD)
9+
10+
## [0.0.1](https://github.com/shmilylty/onefroall/releases/tag/v0.0.1) - 2019-08-01
11+
### Added
12+
- 添加检查crossdomain.xml收集子域功能
13+
- 添加检查域名证书收集子域功能
14+
- 添加检查内容安全策略头收集子域功能
15+
- 添加域传送利用功能
16+
- 添加子域收集功能(搜索引擎,DNS数据集,证书透明度,网上爬虫档案)
17+
- 添加子域爆破功能
18+
- 添加数据库导出功能

CODE_OF_CONDUCT.md

+51-76
Original file line numberDiff line numberDiff line change
@@ -1,76 +1,51 @@
1-
# Contributor Covenant Code of Conduct
2-
3-
## Our Pledge
4-
5-
In the interest of fostering an open and welcoming environment, we as
6-
contributors and maintainers pledge to making participation in our project and
7-
our community a harassment-free experience for everyone, regardless of age, body
8-
size, disability, ethnicity, sex characteristics, gender identity and expression,
9-
level of experience, education, socio-economic status, nationality, personal
10-
appearance, race, religion, or sexual identity and orientation.
11-
12-
## Our Standards
13-
14-
Examples of behavior that contributes to creating a positive environment
15-
include:
16-
17-
* Using welcoming and inclusive language
18-
* Being respectful of differing viewpoints and experiences
19-
* Gracefully accepting constructive criticism
20-
* Focusing on what is best for the community
21-
* Showing empathy towards other community members
22-
23-
Examples of unacceptable behavior by participants include:
24-
25-
* The use of sexualized language or imagery and unwelcome sexual attention or
26-
advances
27-
* Trolling, insulting/derogatory comments, and personal or political attacks
28-
* Public or private harassment
29-
* Publishing others' private information, such as a physical or electronic
30-
address, without explicit permission
31-
* Other conduct which could reasonably be considered inappropriate in a
32-
professional setting
33-
34-
## Our Responsibilities
35-
36-
Project maintainers are responsible for clarifying the standards of acceptable
37-
behavior and are expected to take appropriate and fair corrective action in
38-
response to any instances of unacceptable behavior.
39-
40-
Project maintainers have the right and responsibility to remove, edit, or
41-
reject comments, commits, code, wiki edits, issues, and other contributions
42-
that are not aligned to this Code of Conduct, or to ban temporarily or
43-
permanently any contributor for other behaviors that they deem inappropriate,
44-
threatening, offensive, or harmful.
45-
46-
## Scope
47-
48-
This Code of Conduct applies both within project spaces and in public spaces
49-
when an individual is representing the project or its community. Examples of
50-
representing a project or community include using an official project e-mail
51-
address, posting via an official social media account, or acting as an appointed
52-
representative at an online or offline event. Representation of a project may be
53-
further defined and clarified by project maintainers.
54-
55-
## Enforcement
56-
57-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58-
reported by contacting the project team at [email protected]. All
59-
complaints will be reviewed and investigated and will result in a response that
60-
is deemed necessary and appropriate to the circumstances. The project team is
61-
obligated to maintain confidentiality with regard to the reporter of an incident.
62-
Further details of specific enforcement policies may be posted separately.
63-
64-
Project maintainers who do not follow or enforce the Code of Conduct in good
65-
faith may face temporary or permanent repercussions as determined by other
66-
members of the project's leadership.
67-
68-
## Attribution
69-
70-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71-
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72-
73-
[homepage]: https://www.contributor-covenant.org
74-
75-
For answers to common questions about this code of conduct, see
76-
https://www.contributor-covenant.org/faq
1+
# 参与者公约
2+
3+
## 我们的承诺
4+
5+
为建设开放友好的环境,我们贡献者和维护者承诺:不论年龄、体型、身体健全与否、民族、性征、性别认同与表征、经验水平、教育程度、社会地位、国籍、相貌、种族、信仰、性取向,我们项目和社区的参与者皆免于骚扰。
6+
7+
## 我们的准则
8+
9+
有助于创造积极环境的行为包括但不限于:
10+
11+
* 措辞友好且包容
12+
* 尊重不同的观点和经验
13+
* 耐心接受有益批评
14+
* 关注对社区最有利的事情
15+
* 与社区其他成员友善相处
16+
17+
参与者不应采取的行为包括但不限于:
18+
19+
* 发布与性有关的言论或图像、不受欢迎地献殷勤
20+
* 捣乱/煽动/造谣行为、侮辱/贬损的评论、人身及政治攻击
21+
* 公开或私下骚扰
22+
* 未经明确授权便发布他人的资料,如住址、电子邮箱等
23+
* 其他有理由认定为违反职业操守的不当行为
24+
25+
## 我们的义务
26+
27+
项目维护者有义务诠释何谓“妥当行为”,并妥善公正地纠正已发生的不当行为。
28+
29+
项目维护者有权利和义务去删除、编辑、拒绝违背本行为标准的评论(comments)、提交(commits)、代码、wiki 编辑、问题(issues)等贡献;项目维护者可暂时或永久地封禁任何他们认为行为不当、威胁、冒犯、有害的参与者。
30+
31+
## 适用范围
32+
33+
本行为标准适用于本项目。当有人代表本项目或本社区时,本标准亦适用于此人所处的公共平台。
34+
35+
代表本项目或本社区的情形包括但不限于:使用项目的官方电子邮件、通过官方媒体账号发布消息、作为指定代表参与在线或线下活动等。
36+
37+
代表本项目的行为可由项目维护者进一步定义及解释。
38+
39+
## 贯彻落实
40+
41+
可以致信[[email protected]],向项目团队举报滥用、骚扰及不当行为。
42+
43+
维护团队将审议并调查全部投诉,妥善地予以必要的回应。项目团队有义务保密举报者信息。具体执行方针或将另行发布。
44+
45+
未切实遵守或执行本行为标准的项目维护人员,经项目负责人或其他成员决议,可能被暂时或永久地剥夺参与本项目的资格。
46+
47+
## 来源
48+
49+
本行为标准改编自[参与者公约](https://www.contributor-covenant.org)的1.4版本,可[在此](https://www.contributor-covenant.org/zh-cn/version/1/4/code-of-conduct.html)查阅。
50+
51+
You can view the Contributor Covenant Translations [here](https://www.contributor-covenant.org/translations).

CONTRIBUTING.md

+42-1
Original file line numberDiff line numberDiff line change
@@ -1 +1,42 @@
1-
1+
# Contribution Guidelines
2+
3+
Before opening any issues or proposing any pull requests and to get the greatest chance of helpful responses, please observe the following notes.
4+
5+
## Good Bug Reports
6+
7+
Please be aware of the following things when filing bug reports:
8+
9+
1. Avoid raising duplicate issues. *Please* use the GitHub issue search feature
10+
to check whether your bug report or feature request has been mentioned in
11+
the past. Duplicate bug reports and feature requests are a huge maintenance
12+
burden on the limited resources of the project. If it is clear from your
13+
report that you would have struggled to find the original, that's ok, but
14+
if searching for a selection of words in your issue title would have found
15+
the duplicate then the issue will likely be closed extremely abruptly.
16+
2. When filing bug reports about exceptions or tracebacks, please include the
17+
*complete* traceback. Partial tracebacks, or just the exception text, are
18+
not helpful. Issues that do not contain complete tracebacks may be closed
19+
without warning.
20+
3. Make sure you provide a suitable amount of information to work with. This
21+
means you should provide:
22+
23+
- Guidance on **how to reproduce the issue**. Ideally, this should be a
24+
*small* code sample that can be run immediately by the maintainers.
25+
Failing that, let us know what you're doing, how often it happens, what
26+
environment you're using, etc. Be thorough: it prevents us needing to ask
27+
further questions.
28+
- Tell us **what you expected to happen**. When we run your example code,
29+
what are we expecting to happen? What does "success" look like for your
30+
code?
31+
- Tell us **what actually happens**. It's not helpful for you to say "it
32+
doesn't work" or "it fails". Tell us *how* it fails: do you get an
33+
exception? A hang? A non-200 status code? How was the actual result
34+
different from your expected result?
35+
- Tell us **what version of OneForAll you're using**, and
36+
**how you installed it**. Different versions of Requests behave
37+
differently and have different bugs, and some distributors of Requests
38+
ship patches on top of the code we supply.
39+
40+
If you do not provide all of these things, it will take us much longer to
41+
fix your problem. If we ask you to clarify these and you never respond, we
42+
will close your issue without fixing it.

CONTRIBUTORS.md

+7
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
# OneForAll贡献者
2+
3+
* **[Jing Ling](https://github.com/shmilylty)**
4+
* 核心开发
5+
6+
* **[Black Star](https://github.com/shmilylty)**
7+
* 模块贡献

0 commit comments

Comments
 (0)