kryptheon 0.1.44 → 0.1.46
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +40 -0
- package/bin/kryptheon.js +3436 -3242
- package/kryptheon-dashboard-page.js +101 -10
- package/kryptheon-dashboard.html +7 -1
- package/kryptheon-dashboard.js +1121 -1009
- package/kryptheon-edge.js +777 -0
- package/kryptheon-look.js +1 -1
- package/kryptheon-probe-fixture.js +267 -0
- package/kryptheon-probe-reporter.js +29 -0
- package/kryptheon-probe.config.js +37 -0
- package/kryptheon-probe.js +274 -0
- package/kryptheon-replay.js +0 -0
- package/package.json +10 -4
package/README.md
CHANGED
|
@@ -225,6 +225,46 @@ is "verification required", ranked HIGH when the value comes from a server
|
|
|
225
225
|
response or an error message, MEDIUM when the code alone cannot say. The fix
|
|
226
226
|
prompt for each one names the file, line and value.
|
|
227
227
|
|
|
228
|
+
## Unusual inputs
|
|
229
|
+
|
|
230
|
+
```
|
|
231
|
+
npx kryptheon edge
|
|
232
|
+
```
|
|
233
|
+
|
|
234
|
+
Replays your recorded forms with one field at a time given a value people
|
|
235
|
+
type by accident: nothing, 5000 characters, text with an HTML tag, emoji, a
|
|
236
|
+
negative number, a date that does not exist. It reports only what the run
|
|
237
|
+
proves:
|
|
238
|
+
|
|
239
|
+
- the page threw an error that the plain replay did not;
|
|
240
|
+
- the server answered 5xx where the plain replay did not;
|
|
241
|
+
- the app saved a value it should not take - shown as the field's value in
|
|
242
|
+
the plain replay's request next to the same field in this one, with the
|
|
243
|
+
2xx answer;
|
|
244
|
+
- a tag typed into a field came back as a real element on the page (the app
|
|
245
|
+
does not escape it).
|
|
246
|
+
|
|
247
|
+
A form that refuses a value is doing its job, so a replay that fails after it
|
|
248
|
+
is said as "held", never as a problem. A "too many requests" (429) answer
|
|
249
|
+
means that value was not tested. A 5xx or page error is run a second time
|
|
250
|
+
before it is called a problem.
|
|
251
|
+
|
|
252
|
+
**It adds test data to your app, and leaves it there.** So it never runs on
|
|
253
|
+
its own - not after a change, not at night - only when you run the command and
|
|
254
|
+
say yes, or press its button in the dashboard. Most of what it types contains
|
|
255
|
+
the word `kryptheon-test`; every write that was accepted is listed at the end.
|
|
256
|
+
It never creates an account, never changes the sign-in, and never prints or
|
|
257
|
+
keeps a password. At most 40 runs per press, with a pause between runs, and
|
|
258
|
+
Stop in the dashboard ends it part way.
|
|
259
|
+
|
|
260
|
+
Run it against your app on your own computer, or your own test copy. `--yes`
|
|
261
|
+
says yes in advance, and only works when every address is on this computer.
|
|
262
|
+
For any other address - including a database your local page saves to, which
|
|
263
|
+
it notices on the first replay - you are warned and must answer yourself.
|
|
264
|
+
|
|
265
|
+
`npx kryptheon recheck <id>` tries a finding's value again: FIXED, or STILL
|
|
266
|
+
OPEN with the new proof.
|
|
267
|
+
|
|
228
268
|
## What goes where
|
|
229
269
|
|
|
230
270
|
Only your recordings go in your project, in `tests/`. Everything Kryptheon
|