fedramp-automation
cli
Our great sponsors
| fedramp-automation | cli | |
|---|---|---|
| 3 | 3 | |
| 246 | 134 | |
| 4.1% | 1.5% | |
| 0.0 | 0.0 | |
| 11 days ago | about 3 years ago | |
| TypeScript | TypeScript | |
| 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.
fedramp-automation
-
Using the FedRAMP Automation (OSCAL) GitHub Release
I've been reading this guide to learn more about the XML and JSON files included in the FedRAMP Automation release, but I'm having a hard time making sense of it (I'm not a software developer).
-
FedRAMP NIST 800-53 Rev 5 SSP Templates
I've been checking in on this github pull request-- I think the rev 5 baselines will be official when this is approved/merged https://github.com/GSA/fedramp-automation/pull/389
- What's the biggest limitation to the use of OSCAL?
cli
-
Show HN: We made a CLI and API to automate inbound email
Hi HN! We're a 5 person team working on simplifying the creation of email apps. Right now, most email services focus on outbound emails (newsletters, transactional, delivery), but that doesn't solve the fact that we all hate receiving them.
Mailscript lets you create programmable email addresses. It works headless, via the CLI, API (we use Swagger to support most languages). You can even run it as a daemon on a server (to run functions when emails arrive).
Once you get [email protected], you can create as many aliases as you'd like (including on the fly support for *@username.mailscript.com). Just like in Gmail, we support adding . or +. Every address gets an SMTP key as well, so you can use your favourite email client e.g. Gmail...
We've been working hard on making the CLI and API easy to understand, and take a trigger/actions approach. We even have parsers for GitHub emails (so you can automate Issues, PRs, Actions). You can see what the code looks like in our templates: https://github.com/mailscript/cli/tree/main/packages/templates
Example use cases:
- Join our discussion forum on Discord!
- Mailscript version 0.4.7
What are some alternatives?
OSCAL - Open Security Controls Assessment Language (OSCAL)
spotify-library - Export your Spotify library to JSON via CLI. Supports track genres and audio features
oscal-rest - An initial OpenAPI definition of an OSCAL REST API.
use-force-update - React Hook to force your function component to update
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
use-clippy - React Hook for reading from and writing to the user's clipboard.
oscal-content - NIST SP 800-53 content and other OSCAL content examples
stdoutToJSON - Transforms stdout (standard out) to JSON 📇
appsmith - Platform to build admin panels, internal tools, and dashboards. Integrates with 25+ databases and any API.
n8n - Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
ctix - CLI to generate barrel file for webpack, rollup entrypoint