<commit_before># govready
GovReady provides a dashboard and tools to enhance security for government websites and achieve FISMA compliance.



## Developing

To delete the token and force re-authentication, run this wp-cli command:
```
wp option delete govready_options
```

### Making calls to the GovReady API
```javascript
http://localhost:8080/wp-admin/admin-ajax.php?action=govready_proxy&endpoint=/initialize&method=POST
```
```javascript
jQuery.get(
  ajaxurl, 
  {
    'action': 'govready_proxy',
    'endpoint': '/sites/' + govready.siteId
  }, 
  function(response){
    console.log('Data from the api', response);
  }
);
```<commit_msg>Improving plugin README #14 https://github.com/GovReady/GovReady-CMS-API/issues/16 #18<commit_after># govready
GovReady provides a dashboard and tools to enhance security for government websites and achieve FISMA compliance.

## Overview

The GovReady Agent monitors your WordPress site, domain, and ssl certificate to ensure that you are
following current security best-practices.

The GovReady Dashboard gives you a shared, easy-to-digest overview of the status of security on your
website, including:
* WordPress Core update status
* Contributed plugin update status, with vulnerability warnings from the [WPScan Vulnerability Database](wpvulndb.com)
* Superadmin accounts
* Site uptime monitoring
* The status of your domain and SSL certificate renewals
* A manual measures checklist to be completed periodically to ensure compliance
* A contact info matrix ("who do I contact to change my password", etc)
* Accounts that have not recently logged-in (and may have left your organization)
* Recent WordPress security news
* Recent important Internet security news (such as the recent [HeartBleed bug](http://heartbleed.com/))

`@todo` add screenshot(s)

Note: This plugin is currently under active development and should not be used on production websites.


## Requirements
* cURL must be installed and appear in `php.ini`. [Tutorial to enable cURL in PHP]
(http://www.tomjepson.co.uk/enabling-curl-in-php-php-ini-wamp-xamp-ubuntu/).

---

## Developing

To delete the token and force re-authentication, run this wp-cli command:
```
wp option delete govready_options
```

### Making calls to the GovReady API
```javascript
http://localhost:8080/wp-admin/admin-ajax.php?action=govready_proxy&endpoint=/initialize&method=POST
```
```javascript
jQuery.get(
  ajaxurl, 
  {
    'action': 'govready_proxy',
    'endpoint': '/sites/' + govready.siteId
  }, 
  function(response){
    console.log('Data from the api', response);
  }
);
```


### Example calls to the API
{'fraction_non_alphanumeric': 0.10061208875286917, 'fraction_numerical': 0.005355776587605203, 'mean_word_length': 4.785398230088496, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 1, 'lorem ipsum': 0, 'www.': 1, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '274097', 'n_tokens_mistral': 786, 'n_tokens_neox': 726, 'n_words': 277}