interalia
check-spelling
interalia | check-spelling | |
---|---|---|
4 | 2 | |
45 | 243 | |
- | 3.7% | |
6.2 | 7.8 | |
4 months ago | 13 days ago | |
Shell | Shell | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
interalia
-
I designed and ordered Shavian-only keycaps!
not sure what font that is, but I would use Inter-alia if it already isn't
-
School Poster/๐๐๐ต๐ค ๐๐ด๐๐๐ผ
This font has an extra bold weight you can try https://github.com/Shavian-info/interalia
- Inter Alia - expanded version of the Inter font family to include Shavian alphabet support
-
Introducing Inter Alia | ๐ฆ๐ฏ๐๐ฎ๐ฉ๐๐ฟ๐๐ฆ๐ ยท๐ฆ๐ฏ๐๐ผ ๐ฑ๐ค๐พ
I'd like to introduce Inter Alia, an expansion of the beautiful and popular Inter font to include Shavian alphabet support and old-style figures. It only took 60 years, but Shavian now has a fully-featured font. Please test it - feedback is welcome! https://github.com/Shavian-info/interalia
check-spelling
-
Add check-spelling to a repository
View on GitHub
-
GitHub Actions checkspelling community workflow GitHub_TOKEN leakage via symlink
> If my repo always runs all tests on a PR, could someone just add a PR with a new test that is then run? Thus running their arbitrary code.
Running arbitrary code is inevitable if an action is configured to run on all PRs. People have abused this to run crypto miners and stuff in the past, but this for the most part is merely an annoyance to maintainers, not a security problem. It does become a security problem when arbitrary code execution is allowed with your secrets, including your configured secrets and the read/write GITHUB_TOKEN.
Expanding on the topic of secrets, if you trigger your test from the usual pull_request event, the workflow won't have access to GITHUB_TOKEN or configured secrets, so it's the safe default you should almost always choose. That becomes a problem when you need write access to the repo, e.g. to assign labels or add comments to the PR from the workflow, in which case you have to use the privileged pull_request_target event to expose GITHUB_TOKEN and secrets. pull_request_target by default runs in the context of the base of the PR, so there's still no arbitrary code, but you can explicitly check out the PR in that context, and when you do, your secrets are potentially exposed to arbitrary code. If you execute that arbitrary code in any job, or like in this case, post the content of effectively any file on disk as directed by an attacker, boom, owned.
Therefore, you should
- Avoid pull_request_target unless white access to the repo and/or access to configured secrets is absolutely necessary;
- When using pull_request_target, avoid checking out untrusted code;
- If it's absolutely necessary to check out untrusted code, make absolutely sure that the untrusted code isn't executed in any way, and that your trusted handling code can't be tricked by untrusted content in any way, like an arbitrary symlink. This is of course difficult to verify.
In this specific case, the fix seems to be checking that the absolute path of the untrusted advice.txt is within GITHUB_WORKSPACE (https://github.com/check-spelling/check-spelling/commit/4363...). IMO that's a wrong fix only covering the symptom. The real cause is using untrusted configuration files at all; why not make a copy of the trusted version of configuration files and use those instead???
GitHub has an article about security considerations here: https://securitylab.github.com/research/github-actions-preve...
What are some alternatives?
sans-indexes - Indexes for SANS Courses and GIAC Certifications
did_you_mean - The gem that has been saving people from typos since 2014
advisories
PHP-Spellchecker - ๐๐๐ PHP Library providing an easy way to spellcheck multiple sources of text by many spellcheckers
ohmyzsh - ๐ A delightful community-driven (with 2,300+ contributors) framework for managing your zsh configuration. Includes 300+ optional plugins (rails, git, macOS, hub, docker, homebrew, node, php, python, etc), 140+ themes to spice up your morning, and an auto-update tool so that makes it easy to keep up with the latest updates from the community.
Windows Terminal - The new Windows Terminal and the original Windows console host, all in the same place!
winget-cli - WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
Knot Resolver - Knot Resolver - resolve DNS names like it's 2024
PowerToys - Windows system utilities to maximize productivity
hammerspoon - Staggeringly powerful macOS desktop automation with Lua
spell-check-this - Template for adding check-spelling action to a repository
spelling - Custom spelling tool - the basis for https://github.com/check-spelling/check-spelling