Language: English
Ribbit Capital · Website findings
Ribbit Capital’s application form software was updated
Seven JavaScript files changed on Ribbit’s application page. The archived code shows a new back-link setting, token-management code removed from one bundle, and five supporting files with updated asset references.
TIBBIR Universe · Published 2026-11-09T21:48:23.527Z · Updated 2026-11-09T21:48:23.527Z
A symbolic view of seven changed files under examination. Editorial illustration, not a captured website. · Editorial illustration01 / THE FINDINGS
The page stayed the same. Some of its loaded software did not.
The monitor recorded this change on 8 November 2026 at 22:01:45 UTC, after the preceding successful page capture at 21:00:56 UTC. That is an observation window, not an exact deployment time.
Ribbit’s Pathfinder application page loaded six changed form-related JavaScript files and a changed Google analytics script. The main form bundle identifies itself as Paperform software. CloudFront hosts those assets; its hostname alone does not identify who wrote or deployed them.
The saved application instructions still ask for two video answers under two minutes each and a written answer under 300 words. The outer page’s HTML is byte-for-byte identical. Neither finding rules out changes that appear only while recording, uploading or submitting a response.
02 / THE FINDINGS
A back-link setting is passed into the form configuration.
The main form bundle now copies back_href from an existing value into a configuration object. The added line is small, but it is a concrete change beyond a filename refresh.
The name suggests a destination for return navigation. For example, software could use such a setting to send someone back to another page. The captured difference establishes the assignment; it does not show whether this particular application supplies the setting or displays a back link.
form-form-rchwiESS.js
− Before · javascript · formatted line 40320No removed lines in this excerpt.
Original before source ↗+ After · javascript · formatted line 40314 back_href: d.back_href,
Original after source ↗ Compared with a content-matched earlier file. This is comparison evidence, not proof of a rename.
03 / THE FINDINGS
Token-management code leaves this captured bundle.
The previous file contains action definitions and helpers for listing, creating and deleting personal access tokens. Their action registrations disappear from the later file, as the excerpt shows.
This is a statement about the contents of one JavaScript bundle. It does not establish that Paperform removed token management from its service, that an applicant had access to those functions, or that any account token was deleted. The code could still exist elsewhere.
form-form-rchwiESS.js
− Before · javascript · formatted line 47453 loadScopes = libExports.createAction(passport.LOAD_SCOPES, loadScopes$1),
loadTokens = libExports.createAction(passport.LOAD_TOKENS, loadTokens$1),
createToken = libExports.createAction(passport.CREATE_TOKEN, createToken$1),
deleteToken = libExports.createAction(passport.DELETE_TOKEN, deleteToken$1),
Original before source ↗+ After · javascript · formatted line 47398No added lines in this excerpt.
Original after source ↗ Compared with a content-matched earlier file. This is comparison evidence, not proof of a rename.
04 / THE FINDINGS
Some differences are changes to names and packaging.
Shared request helpers change from get$1 and post$1 to get and post, with corresponding call-site changes. The GET helper retains the same exported alias. A renamed helper does not by itself establish a change in what a request does.
The field-reordering code also appears differently arranged in the comparison. The supplied analysis found its logic preserved; this is not evidence of a new form-editing capability for applicants.
form-form-rchwiESS.js
− Before · javascript · formatted line 33136const get$1 = (h, ...m) => mt(null, [h, ...m], function*(d, p = {}) {
Original before source ↗+ After · javascript · formatted line 33130const get = (h, ...m) => mt(null, [h, ...m], function*(d, p = {}) {
Original after source ↗ Compared with a content-matched earlier file. This is comparison evidence, not proof of a rename.
05 / THE FINDINGS
Five supporting files point to newly named assets.
The dropdown, file-handling, upload, image-type and react-select files match after normalising their hashed asset references. Their differences are consistent with repackaging rather than changed component logic.
The upload excerpt illustrates this distinction: the imported image-type and file-handling modules have different generated filenames. That is not evidence of an upload fix. A dependency can still change elsewhere, which is why the main form bundle needs its own comparison.
06 / THE FINDINGS
The Google script changed separately.
The archived Google tag response also differs. One configuration value changes from an empty string to google.fr; other changed values include regional labels. This is visible in the source even though the earlier summary did not include Google’s detailed differences.
A different response from an analytics service can reflect the circumstances of a capture. These literals do not establish a deliberate settings change by Ribbit, a new tracking feature, or a change to application processing.
07 / THE FINDINGS
What applicants can—and cannot—take from this.
The evidence is consistent with an update to hosted form software alongside a separate analytics response change. It does not establish that Ribbit edited its own repository or manually upgraded a plugin.
The back-link assignment is the clearest small configuration change shown here. The token-related removals reduce the code present in this bundle, while the five supporting files retain their logic after asset references are normalised. No improvement to recording, uploads or submission has been demonstrated.
The excerpts below each finding are formatted for reading and linked to the original archived files. Their line numbers refer to the formatted source. The earlier and later form files were paired by content; that comparison is not proof of a rename.
Documented
- The captured application instructions and outer-page HTML are unchanged.
- The main form bundle adds back_href to a configuration object.
- Token-management helpers and action registrations disappear from this captured bundle.
- Five supporting form files differ only in hashed asset references after normalisation.
- The archived Google tag response contains changed configuration values.
Possible interpretations
- The pattern is consistent with an update to Paperform’s hosted software plus a separate Google analytics response change. Who initiated either change is not established.
Still unknown
- Whether this form supplies or uses back_href, and whether applicants see any navigation change.
- Whether token-management code moved to another file or remains elsewhere in Paperform.
- Why the Google response differs and what practical effect, if any, those differences have.
- Whether recording, uploads or submission behave differently; no interaction test is supplied.
- The exact deployment time and who initiated the changes.
Sources and limits.
- Ribbit Capital · before capture
Saved public page before this change. It establishes captured wording and links, not server-side behaviour.
- Ribbit Capital · after capture
Saved public page after this change. It establishes captured wording and links, not server-side behaviour.
- form-Dropdown-ChXKf-xa.js · before
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-Dropdown-ChXKf-xa.js. This establishes captured source, not whether this page exercises every code path.
- form-Dropdown-BKkK0udy.js · after
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-Dropdown-BKkK0udy.js. This establishes captured source, not whether this page exercises every code path.
- form-file-BIwsbrP6.js · before
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-file-BIwsbrP6.js. This establishes captured source, not whether this page exercises every code path.
- form-file-D5h3ZFBN.js · after
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-file-D5h3ZFBN.js. This establishes captured source, not whether this page exercises every code path.
- form-FileUpload-mGadoIXn.js · before
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-FileUpload-mGadoIXn.js. This establishes captured source, not whether this page exercises every code path.
- form-FileUpload-CSiTF0fI.js · after
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-FileUpload-CSiTF0fI.js. This establishes captured source, not whether this page exercises every code path.
- form-form-Bzkfy-Tu.js · before
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-form-Bzkfy-Tu.js. This establishes captured source, not whether this page exercises every code path.
- form-form-rchwiESS.js · after
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-form-rchwiESS.js. This establishes captured source, not whether this page exercises every code path.
- form-imageAcceptTypes-_T1hrs9t.js · before
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-imageAcceptTypes-_T1hrs9t.js. This establishes captured source, not whether this page exercises every code path.
- form-imageAcceptTypes-C3mB254z.js · after
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-imageAcceptTypes-C3mB254z.js. This establishes captured source, not whether this page exercises every code path.
- form-react-select.es-BNB1lDCB.js · before
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-react-select.es-BNB1lDCB.js. This establishes captured source, not whether this page exercises every code path.
- form-react-select.es-BGPpps6o.js · after
Archived javascript bytes loaded from https://duube1y6ojsji.cloudfront.net/form-react-select.es-BGPpps6o.js. This establishes captured source, not whether this page exercises every code path.
- js · before
Archived javascript bytes loaded from https://www.googletagmanager.com/gtag/js?id=G-NXKKWFZ2DG. This establishes captured source, not whether this page exercises every code path.
- js · after
Archived javascript bytes loaded from https://www.googletagmanager.com/gtag/js?id=G-NXKKWFZ2DG. This establishes captured source, not whether this page exercises every code path.
- apply · before
Archived html bytes loaded from https://www.ribbitcap.com/pathfinder/apply. This establishes captured source, not whether this page exercises every code path.