Skip to content

Commit b202703

Browse files
Fix typo in NIST National Vulnerability Database readme
1 parent 5302353 commit b202703

File tree

1 file changed

+1
-1
lines changed
  • independent-publisher-connectors/NIST National Vulnerability Database

1 file changed

+1
-1
lines changed

independent-publisher-connectors/NIST National Vulnerability Database/readme.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ https://nvd.nist.gov/developers
2525
## Known Issues and Limitations
2626
* When filtering by date, please note the format. As it is unlikely you need to filter based on time, I suggest you specify 000 for sub-seconds and use hh:mm for UTC offset. Eg. For Power Automate flows, this is an example of correctly specifying a date with no UTC offset. formatDateTime(utcNow(), 'yyyy-MM-ddTHH:mm:ss:000 UTC+00:00')
2727

28-
* There are a large number of vulnerabilities stored in a highly granular way. You will need to filter your results and learn the schema to apply filters. E.g Filtering by CPE Match string or CVE match string is documented (here)[http://cpe.mitre.org/specification/index.html]
28+
* There are a large number of vulnerabilities stored in a highly granular way. You will need to filter your results and learn the schema to apply filters. E.g Filtering by CPE Match string or CVE match string is documented [here](http://cpe.mitre.org/specification/index.html)
2929

3030
* Each API Key is associated with a single email address. If an email address is used to request an additional API key, clicking the single-use hyperlink will invalidate the key previously associated with that email address. The key will not be invalidated if the email is used to request another key, but the link is not opened. There is no process for retrieving a forgotten key.
3131

0 commit comments

Comments
 (0)