-
Before a stable version of orion is released, an audit should be done. Preferably of the whole library, though it may end up only being partly. This depends on the financial means available.
Edit:…
brycx updated
3 years ago
-
-
### Checklist
- [x] I have searched for existing issues for issues like this one. The issue has not been posted. (Duplicate reports slow down development.)
- [ ] I have provided reproducable ste…
-
Right now, we have medium-semantic markup and one aria tag. That is not a11y. We can and must do better.
wlonk updated
5 years ago
-
Add automatic audit table logs.
-
1. Inactive/Active project audits: We need to do another audit. Which Projects are active and non-active. I need a list so we can update the inventory.
See first audit below:
- https://docs.google.c…
-
We should get a security audit at least before open beta.
ghost updated
9 years ago
-
We should do a basic penetration test and internal code audit so that we don't get hacked and can harden out application. This will also become more important once we fix #5 and if we have users loggi…
-
We should perform a quick security audit for our application. Including manual and automated testing (e.g. [Vega Report](https://subgraph.com/vega/index.en.html)).
The servers are already being sca…
-
When making sure all the dependencies are up to date for each milestone, we may also want to run something like [**depcheck**](http://npm.im/depcheck) to make sure we don't have any unused dependencie…