Gathering detailed insights and metrics for textlint-rule-ja-no-successive-word
Gathering detailed insights and metrics for textlint-rule-ja-no-successive-word
Gathering detailed insights and metrics for textlint-rule-ja-no-successive-word
Gathering detailed insights and metrics for textlint-rule-ja-no-successive-word
npm install textlint-rule-ja-no-successive-word
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
6 Stars
46 Commits
1 Forks
3 Watching
3 Branches
4 Contributors
Updated on 19 Nov 2024
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
4.7%
3,634
Compared to previous day
Last week
8.8%
19,195
Compared to previous week
Last month
8.8%
80,883
Compared to previous month
Last year
32.8%
839,511
Compared to previous year
2
1
同一の単語(厳密には形態素解析した結果のToken)が間違えて連続しているのを見つけるtextlintルール。 入力ミスによる同じ単語が連続している問題を発見します。
OK:
これは問題ない文章です。
すもももももももものうち
111回目の問題
フレームレートが落ちて動作がカクカクしてきた
NG:
これはは問題ある文章です。
これは問題あるある文章です
Install with npm:
npm install textlint-rule-ja-no-successive-word
Via .textlintrc
(Recommended)
1{ 2 "rules": { 3 "ja-no-successive-word": true 4 } 5}
Via CLI
textlint --rule ja-no-successive-word README.md
オプションのデフォルト値
1{ 2 "rules": { 3 "ja-no-successive-word": { 4 // オノマトペを許可する 5 // 制限: オノマトペを判定する方法がないため、同じカタカナの語が連続したものをオノマトペとして扱う 6 // 例) カクカク、ドキドキ、ビリビリ 7 // https://ja.wikipedia.org/wiki/%E6%93%AC%E5%A3%B0%E8%AA%9E 8 allowOnomatopee: true, 9 10 // 許可する単語 11 // RegExp-like Stringを使用可能 12 allow: [] 13 } 14 } 15}
allowOnomatopee: boolean
true
allow
: string[]
[]
See Releases page.
Install devDependencies and Run npm test
:
npm i -d && npm test
Pull requests and stars are always welcome.
For bugs and feature requests, please create an issue.
git checkout -b my-new-feature
git commit -am 'Add some feature'
git push origin my-new-feature
MIT © azu
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Reason
Found 1/17 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
13 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More