Skip to content

Commit 8f6d4f1

Browse files
feat(audits): Every audit should have a globally unique ID (#49)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 parent fae7e59 commit 8f6d4f1

File tree

20 files changed

+1382
-926
lines changed

20 files changed

+1382
-926
lines changed

docs/interfaces/audits_common.Audit.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ The test function will throw only if the error is fatal.
1313
### Properties
1414

1515
- [fn](audits_common.Audit.md#fn)
16+
- [id](audits_common.Audit.md#id)
1617
- [name](audits_common.Audit.md#name)
1718

1819
## Properties
@@ -31,6 +32,15 @@ The test function will throw only if the error is fatal.
3132

3233
___
3334

35+
### id
36+
37+
**id**: `string`
38+
39+
Uniquely represents the audit. Helps with pinning audits
40+
without depending on the human readable audit name.
41+
42+
___
43+
3444
### name
3545

3646
**name**: \`MUST ${string}\` \| \`SHOULD ${string}\` \| \`MAY ${string}\`

docs/interfaces/audits_common.AuditFail.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,23 @@ is therefore not compliant.
1515

1616
### Properties
1717

18+
- [id](audits_common.AuditFail.md#id)
1819
- [name](audits_common.AuditFail.md#name)
1920
- [reason](audits_common.AuditFail.md#reason)
2021
- [response](audits_common.AuditFail.md#response)
2122
- [status](audits_common.AuditFail.md#status)
2223

2324
## Properties
2425

26+
### id
27+
28+
**id**: `string`
29+
30+
Uniquely represents the failing audit. Helps with pinning audits
31+
without depending on the human readable audit name.
32+
33+
___
34+
2535
### name
2636

2737
**name**: \`MUST ${string}\` \| \`SHOULD ${string}\` \| \`MAY ${string}\`

docs/interfaces/audits_common.AuditOk.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,21 @@ Indicates that the audit was successful.
1010

1111
### Properties
1212

13+
- [id](audits_common.AuditOk.md#id)
1314
- [name](audits_common.AuditOk.md#name)
1415
- [status](audits_common.AuditOk.md#status)
1516

1617
## Properties
1718

19+
### id
20+
21+
**id**: `string`
22+
23+
Uniquely represents the passing audit. Helps with pinning audits
24+
without depending on the human readable audit name.
25+
26+
___
27+
1828
### name
1929

2030
**name**: \`MUST ${string}\` \| \`SHOULD ${string}\` \| \`MAY ${string}\`

implementations/apollo-server/README.md

Lines changed: 78 additions & 78 deletions
Large diffs are not rendered by default.

implementations/deno/README.md

Lines changed: 78 additions & 78 deletions
Large diffs are not rendered by default.

implementations/express-graphql/README.md

Lines changed: 78 additions & 78 deletions
Large diffs are not rendered by default.

implementations/graph-client/README.md

Lines changed: 78 additions & 78 deletions
Original file line numberDiff line numberDiff line change
@@ -6,82 +6,82 @@ _* This report was auto-generated by graphql-http_
66
-**78** pass
77

88
## Passing
9-
1. SHOULD accept application/graphql-response+json and match the content-type
10-
2. MUST accept application/json and match the content-type
11-
3. SHOULD accept \*/\* and use application/json for the content-type
12-
4. SHOULD assume application/json content-type when accept is missing
13-
5. MUST use utf-8 encoding when responding
14-
6. MUST accept utf-8 encoded request
15-
7. MUST assume utf-8 in request if encoding is unspecified
16-
8. MUST accept POST requests
17-
9. MAY accept application/x-www-form-urlencoded formatted GET requests
18-
10. MAY NOT allow executing mutations on GET requests
19-
11. SHOULD respond with 4xx status code if content-type is not supplied on POST requests
20-
12. MUST accept application/json POST requests
21-
13. MUST require a request body on POST
22-
14. SHOULD use 400 status code on missing {query} parameter when accepting application/graphql-response+json
23-
15. SHOULD use 200 status code with errors field on missing {query} parameter when accepting application/json
24-
16. SHOULD use 400 status code on object {query} parameter when accepting application/graphql-response+json
25-
17. SHOULD use 400 status code on number {query} parameter when accepting application/graphql-response+json
26-
18. SHOULD use 400 status code on boolean {query} parameter when accepting application/graphql-response+json
27-
19. SHOULD use 400 status code on array {query} parameter when accepting application/graphql-response+json
28-
20. SHOULD use 200 status code with errors field on object {query} parameter when accepting application/json
29-
21. SHOULD use 200 status code with errors field on number {query} parameter when accepting application/json
30-
22. SHOULD use 200 status code with errors field on boolean {query} parameter when accepting application/json
31-
23. SHOULD use 200 status code with errors field on array {query} parameter when accepting application/json
32-
24. SHOULD allow string {query} parameter when accepting application/graphql-response+json
33-
25. MUST allow string {query} parameter when accepting application/json
34-
26. SHOULD use 400 status code on object {operationName} parameter when accepting application/graphql-response+json
35-
27. SHOULD use 400 status code on number {operationName} parameter when accepting application/graphql-response+json
36-
28. SHOULD use 400 status code on boolean {operationName} parameter when accepting application/graphql-response+json
37-
29. SHOULD use 400 status code on array {operationName} parameter when accepting application/graphql-response+json
38-
30. SHOULD use 200 status code with errors field on object {operationName} parameter when accepting application/json
39-
31. SHOULD use 200 status code with errors field on number {operationName} parameter when accepting application/json
40-
32. SHOULD use 200 status code with errors field on boolean {operationName} parameter when accepting application/json
41-
33. SHOULD use 200 status code with errors field on array {operationName} parameter when accepting application/json
42-
34. SHOULD allow string {operationName} parameter when accepting application/graphql-response+json
43-
35. MUST allow string {operationName} parameter when accepting application/json
44-
36. SHOULD allow null {variables} parameter when accepting application/graphql-response+json
45-
37. MUST allow null {variables} parameter when accepting application/json
46-
38. SHOULD allow null {operationName} parameter when accepting application/graphql-response+json
47-
39. MUST allow null {operationName} parameter when accepting application/json
48-
40. SHOULD allow null {extensions} parameter when accepting application/graphql-response+json
49-
41. MUST allow null {extensions} parameter when accepting application/json
50-
42. SHOULD use 400 status code on string {variables} parameter when accepting application/graphql-response+json
51-
43. SHOULD use 400 status code on number {variables} parameter when accepting application/graphql-response+json
52-
44. SHOULD use 400 status code on boolean {variables} parameter when accepting application/graphql-response+json
53-
45. SHOULD use 400 status code on array {variables} parameter when accepting application/graphql-response+json
54-
46. SHOULD use 200 status code with errors field on string {variables} parameter when accepting application/json
55-
47. SHOULD use 200 status code with errors field on number {variables} parameter when accepting application/json
56-
48. SHOULD use 200 status code with errors field on boolean {variables} parameter when accepting application/json
57-
49. SHOULD use 200 status code with errors field on array {variables} parameter when accepting application/json
58-
50. SHOULD allow map {variables} parameter when accepting application/graphql-response+json
59-
51. MUST allow map {variables} parameter when accepting application/json
60-
52. MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/graphql-response+json
61-
53. MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/json
62-
54. SHOULD use 400 status code on string {extensions} parameter when accepting application/graphql-response+json
63-
55. SHOULD use 400 status code on number {extensions} parameter when accepting application/graphql-response+json
64-
56. SHOULD use 400 status code on boolean {extensions} parameter when accepting application/graphql-response+json
65-
57. SHOULD use 400 status code on array {extensions} parameter when accepting application/graphql-response+json
66-
58. SHOULD use 200 status code with errors field on string {extensions} parameter when accepting application/json
67-
59. SHOULD use 200 status code with errors field on number {extensions} parameter when accepting application/json
68-
60. SHOULD use 200 status code with errors field on boolean {extensions} parameter when accepting application/json
69-
61. SHOULD use 200 status code with errors field on array {extensions} parameter when accepting application/json
70-
62. SHOULD allow map {extensions} parameter when accepting application/graphql-response+json
71-
63. MUST allow map {extensions} parameter when accepting application/json
72-
64. SHOULD use 200 status code on JSON parsing failure when accepting application/json
73-
65. SHOULD use 200 status code if parameters are invalid when accepting application/json
74-
66. SHOULD use 200 status code on document parsing failure when accepting application/json
75-
67. SHOULD use 200 status code on document validation failure when accepting application/json
76-
68. SHOULD use 4xx or 5xx status codes on JSON parsing failure when accepting application/graphql-response+json
77-
69. SHOULD use 400 status code on JSON parsing failure when accepting application/graphql-response+json
78-
70. SHOULD use 4xx or 5xx status codes if parameters are invalid when accepting application/graphql-response+json
79-
71. SHOULD use 400 status code if parameters are invalid when accepting application/graphql-response+json
80-
72. SHOULD not contain the data entry if parameters are invalid when accepting application/graphql-response+json
81-
73. SHOULD use 4xx or 5xx status codes on document parsing failure when accepting application/graphql-response+json
82-
74. SHOULD use 400 status code on document parsing failure when accepting application/graphql-response+json
83-
75. SHOULD not contain the data entry on document parsing failure when accepting application/graphql-response+json
84-
76. SHOULD use 4xx or 5xx status codes on document validation failure when accepting application/graphql-response+json
85-
77. SHOULD use 400 status code on document validation failure when accepting application/graphql-response+json
86-
78. SHOULD not contain the data entry on document validation failure when accepting application/graphql-response+json
9+
1. `22EB` SHOULD accept application/graphql-response+json and match the content-type
10+
2. `4655` MUST accept application/json and match the content-type
11+
3. `47DE` SHOULD accept \*/\* and use application/json for the content-type
12+
4. `80D8` SHOULD assume application/json content-type when accept is missing
13+
5. `82A3` MUST use utf-8 encoding when responding
14+
6. `BF61` MUST accept utf-8 encoded request
15+
7. `78D5` MUST assume utf-8 in request if encoding is unspecified
16+
8. `2C94` MUST accept POST requests
17+
9. `5A70` MAY accept application/x-www-form-urlencoded formatted GET requests
18+
10. `9C48` MAY NOT allow executing mutations on GET requests
19+
11. `9ABE` SHOULD respond with 4xx status code if content-type is not supplied on POST requests
20+
12. `03D4` MUST accept application/json POST requests
21+
13. `7267` MUST require a request body on POST
22+
14. `6610` SHOULD use 400 status code on missing {query} parameter when accepting application/graphql-response+json
23+
15. `3715` SHOULD use 200 status code with errors field on missing {query} parameter when accepting application/json
24+
16. `4F50` SHOULD use 400 status code on object {query} parameter when accepting application/graphql-response+json
25+
17. `4F51` SHOULD use 400 status code on number {query} parameter when accepting application/graphql-response+json
26+
18. `4F52` SHOULD use 400 status code on boolean {query} parameter when accepting application/graphql-response+json
27+
19. `4F53` SHOULD use 400 status code on array {query} parameter when accepting application/graphql-response+json
28+
20. `9FE0` SHOULD use 200 status code with errors field on object {query} parameter when accepting application/json
29+
21. `9FE1` SHOULD use 200 status code with errors field on number {query} parameter when accepting application/json
30+
22. `9FE2` SHOULD use 200 status code with errors field on boolean {query} parameter when accepting application/json
31+
23. `9FE3` SHOULD use 200 status code with errors field on array {query} parameter when accepting application/json
32+
24. `34A2` SHOULD allow string {query} parameter when accepting application/graphql-response+json
33+
25. `13EE` MUST allow string {query} parameter when accepting application/json
34+
26. `E3E0` SHOULD use 400 status code on object {operationName} parameter when accepting application/graphql-response+json
35+
27. `E3E1` SHOULD use 400 status code on number {operationName} parameter when accepting application/graphql-response+json
36+
28. `E3E2` SHOULD use 400 status code on boolean {operationName} parameter when accepting application/graphql-response+json
37+
29. `E3E3` SHOULD use 400 status code on array {operationName} parameter when accepting application/graphql-response+json
38+
30. `FB90` SHOULD use 200 status code with errors field on object {operationName} parameter when accepting application/json
39+
31. `FB91` SHOULD use 200 status code with errors field on number {operationName} parameter when accepting application/json
40+
32. `FB92` SHOULD use 200 status code with errors field on boolean {operationName} parameter when accepting application/json
41+
33. `FB93` SHOULD use 200 status code with errors field on array {operationName} parameter when accepting application/json
42+
34. `8161` SHOULD allow string {operationName} parameter when accepting application/graphql-response+json
43+
35. `B8B3` MUST allow string {operationName} parameter when accepting application/json
44+
36. `94B0` SHOULD allow null {variables} parameter when accepting application/graphql-response+json
45+
37. `0220` MUST allow null {variables} parameter when accepting application/json
46+
38. `94B1` SHOULD allow null {operationName} parameter when accepting application/graphql-response+json
47+
39. `0221` MUST allow null {operationName} parameter when accepting application/json
48+
40. `94B2` SHOULD allow null {extensions} parameter when accepting application/graphql-response+json
49+
41. `0222` MUST allow null {extensions} parameter when accepting application/json
50+
42. `69B0` SHOULD use 400 status code on string {variables} parameter when accepting application/graphql-response+json
51+
43. `69B1` SHOULD use 400 status code on number {variables} parameter when accepting application/graphql-response+json
52+
44. `69B2` SHOULD use 400 status code on boolean {variables} parameter when accepting application/graphql-response+json
53+
45. `69B3` SHOULD use 400 status code on array {variables} parameter when accepting application/graphql-response+json
54+
46. `F050` SHOULD use 200 status code with errors field on string {variables} parameter when accepting application/json
55+
47. `F051` SHOULD use 200 status code with errors field on number {variables} parameter when accepting application/json
56+
48. `F052` SHOULD use 200 status code with errors field on boolean {variables} parameter when accepting application/json
57+
49. `F053` SHOULD use 200 status code with errors field on array {variables} parameter when accepting application/json
58+
50. `2EA1` SHOULD allow map {variables} parameter when accepting application/graphql-response+json
59+
51. `28B9` MUST allow map {variables} parameter when accepting application/json
60+
52. `D6D5` MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/graphql-response+json
61+
53. `6A70` MAY allow URL-encoded JSON string {variables} parameter in GETs when accepting application/json
62+
54. `9040` SHOULD use 400 status code on string {extensions} parameter when accepting application/graphql-response+json
63+
55. `9041` SHOULD use 400 status code on number {extensions} parameter when accepting application/graphql-response+json
64+
56. `9042` SHOULD use 400 status code on boolean {extensions} parameter when accepting application/graphql-response+json
65+
57. `9043` SHOULD use 400 status code on array {extensions} parameter when accepting application/graphql-response+json
66+
58. `3680` SHOULD use 200 status code with errors field on string {extensions} parameter when accepting application/json
67+
59. `3681` SHOULD use 200 status code with errors field on number {extensions} parameter when accepting application/json
68+
60. `3682` SHOULD use 200 status code with errors field on boolean {extensions} parameter when accepting application/json
69+
61. `3683` SHOULD use 200 status code with errors field on array {extensions} parameter when accepting application/json
70+
62. `428F` SHOULD allow map {extensions} parameter when accepting application/graphql-response+json
71+
63. `1B7A` MUST allow map {extensions} parameter when accepting application/json
72+
64. `D477` SHOULD use 200 status code on JSON parsing failure when accepting application/json
73+
65. `F5AF` SHOULD use 200 status code if parameters are invalid when accepting application/json
74+
66. `572B` SHOULD use 200 status code on document parsing failure when accepting application/json
75+
67. `FDE2` SHOULD use 200 status code on document validation failure when accepting application/json
76+
68. `60AA` SHOULD use 4xx or 5xx status codes on JSON parsing failure when accepting application/graphql-response+json
77+
69. `2163` SHOULD use 400 status code on JSON parsing failure when accepting application/graphql-response+json
78+
70. `3E36` SHOULD use 4xx or 5xx status codes if parameters are invalid when accepting application/graphql-response+json
79+
71. `17C5` SHOULD use 400 status code if parameters are invalid when accepting application/graphql-response+json
80+
72. `34D6` SHOULD not contain the data entry if parameters are invalid when accepting application/graphql-response+json
81+
73. `865D` SHOULD use 4xx or 5xx status codes on document parsing failure when accepting application/graphql-response+json
82+
74. `556A` SHOULD use 400 status code on document parsing failure when accepting application/graphql-response+json
83+
75. `D586` SHOULD not contain the data entry on document parsing failure when accepting application/graphql-response+json
84+
76. `51FE` SHOULD use 4xx or 5xx status codes on document validation failure when accepting application/graphql-response+json
85+
77. `74FF` SHOULD use 400 status code on document validation failure when accepting application/graphql-response+json
86+
78. `5E5B` SHOULD not contain the data entry on document validation failure when accepting application/graphql-response+json
8787

0 commit comments

Comments
 (0)