Prosecution Insights
Last updated: November 13, 2026
Application No. 19/068,247

SYSTEM AND METHOD FOR CONTEXTUAL SECURITY ANALYSIS OF SOFTWARE ARTIFACTS

Final Rejection §102
Filed
Mar 03, 2025
Examiner
BROWN, ANTHONY D
Art Unit
2408
Tech Center
2400 — Computer Networks
Assignee
Jfrog Ltd.
OA Round
2 (Final)
86%
Grant Probability
Favorable
3-4
OA Rounds
99%
With Interview

Examiner Intelligence

Grants 86% — above average
86%
Career Allowance Rate
751 granted / 878 resolved
+27.5% vs TC avg
Moderate +15% lift
Without
With
+15.0%
Interview Lift
resolved cases with interview
Typical timeline
Avg Prosecution
21 currently pending
Career history
908
Total Applications
across all art units

Office Action

§102
Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Allowable Subject Matter Claims 2, 9 and 16 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims. Response to Arguments Applicant argues that the prior art Plate does not disclose “flagging one or more of the identified third party libraries as vulnerable, each flagged library including a function reaching the vulnerable function, wherein the flagging of one or more of the identified third party libraries as vulnerable comprises associating one or more of the identified third party libraries with the software vulnerability; flagging one or more first party libraries as vulnerable, the flagged one or more first party libraries matching one or more of the flagged third party libraries”, as recited in independent claims. In response to Applicants arguments, the Examiner respectfully disagrees with the applicant and would like to show that Plate discloses flagging one or more of the identified third party libraries as vulnerable, each flagged library including a function reaching the vulnerable function, wherein the flagging of one or more of the identified third party libraries as vulnerable comprises associating one or more of the identified third party libraries with the software vulnerability; flagging one or more first party libraries as vulnerable, the flagged one or more first party libraries matching one or more of the flagged third party libraries. The Examiner points out that Plate discloses at 306, for each fix commit that addresses the vulnerability, the process may identify functions (or code segments) affected by the vulnerability. At 308, for each function (or code segment) that is identified as being affected by the vulnerability, the process may determine which versions include the vulnerability. At 310, for each function (or code segment) that is identified as being affected by the vulnerability, determine which versions include a fix to address the vulnerability (Paragraph 54). Further Plate discloses after receiving the security advisory 134, the AI 123 may become aware of the existence of the vulnerability 136. The AI 123 may analyze the commit histories 122 of each of the third-party libraries 116 to identify one or more fix commits (e.g., the representative fix commit 124(M)) that address the vulnerability 136 (Paragraph 52). Examiner asserts that the third-party libraries and function in Plate is germane to the identified third party libraries and vulnerable function, as described in Applicant’s invention. As such the Examiner maintains the rejection. Claim Rejections - 35 USC § 102 In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status. The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action: A person shall be entitled to a patent unless – (a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention. Claim(s) 1-20 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Plate (US Patent Pub. 2024/0411897) As per claims 1, 8 and 15: Plate discloses a computerized method of contextual security analysis for software artifacts, the method comprising, using a computer processor (see abstract): for each of a plurality of software vulnerabilities, each software vulnerability associated with a vulnerable function, the vulnerable function included in a vulnerable library (Paragraph 52; after receiving the security advisory 134, the AI 123 may become aware of the existence of the vulnerability 136. The AI 123 may analyze the commit histories 122 of each of the third-party libraries 116 to identify one or more fix commits (e.g., the representative fix commit 124(M)) that address the vulnerability 136): identifying one or more third party libraries using the vulnerable library (Paragraph 51; the process determines, based on a security advisory, an existence of a vulnerability. At 304, the process may analyze a commit history to identify one or more fix commits that address the vulnerability); flagging one or more of the identified third party libraries as vulnerable, each flagged library including a function reaching the vulnerable function, wherein the flagging of one or more of the identified third party libraries as vulnerable comprises associating one or more of the identified third party libraries with the software vulnerability (Paragraph 51; At 306, for each fix commit that addresses the vulnerability, the process may identify functions (or code segments) affected by the vulnerability. At 308, for each function (or code segment) that is identified as being affected by the vulnerability, the process may determine which versions include the vulnerability. At 310, for each function (or code segment) that is identified as being affected by the vulnerability, determine which versions include a fix to address the vulnerability); and flagging one or more first party libraries as vulnerable, the flagged one or more first party libraries matching one or more of the flagged third party libraries (Paragraph 52; A code developer or the AI 123 may automatically (without human interaction) modify the project code 104 to use the fixed versions of a function and not use versions of the function that include the vulnerability 136). As per claims 2, 9 and 16: Plate discloses the computerized method of claim 1, comprising, for each of the identified one or more third party libraries: building a reachability graph, the reachability graph including one or more functions of the identified third party library (Paragraph 30; This may done by obtaining packages from package registries, such as Maven Central or npm, and determining whether they include the function 138 in a vulnerable form (e.g., with the vulnerability 136) or a fixed form (e.g., without the vulnerability 136). This comparison can involve the source code representation, abstractions thereof, e.g. abstract syntax trees or control flow graphs, as well as their compiled form); and extracting one or more of the functions from the reachability graph, wherein each of the extracted functions reach the vulnerable function (Paragraph 48; identifying vulnerable code within a project may include extracting components from a fixed commit and determining whether the vulnerability can be reached from an application (e.g., project code). Reachability analysis is used to determine whether a vulnerability is reachable by the application); wherein the flagging of the one or more of the identified third party libraries is performed based on the extracting of the one or more of the functions from the reachability graph (Paragraph 48). As per claims 3, 10 and 17: Plate discloses the computerized method of claim 1, wherein the flagging of one or more of the identified third party libraries as vulnerable comprises storing a database entry in cache memory, the database entry associating the one or more flagged third party libraries and the one or more functions reaching the vulnerable function with the software vulnerability (Paragraph 18-19; identifying and addressing vulnerabilities in third-party library functions and components. The systems and techniques enrich vulnerability descriptions with detailed code-level information, which is typically absent in existing vulnerability databases). As per claims 4, 11 and 18: Plate discloses the computerized method of claim 2, comprising filtering out one or more of the extracted functions, the filtered out functions called from outside of the identified library (Paragraph 20; Using the fix commits as input, the systems and techniques may identify the individual functions that were vulnerable and that have been modified to address the vulnerability). As per claim 5, 12 and 19: Plate discloses the computerized method of claim 1, comprising iteratively repeating, for one or more of the third party libraries flagged as vulnerable, the identifying of one or more third party libraries using the vulnerable library and the flagging of one or more of the identified third party libraries as vulnerable (Paragraph 56; In this way, 404, 408, 412 may be repeated until the machine learning is able to classify the test data 410 with the desired accuracy). As per claims 6, 13 and 20: Plate discloses the computerized method of claim 1, wherein the function reaching the vulnerable function comprises one or more of: a function passing one or more data items into the vulnerable function, a function including a call chain wherein the call chain includes the vulnerable function, and a function included in a software module wherein the software module includes the vulnerable function (Paragraph 28; The function name 125 is a unique identifier of a function (or set of functions) associated with the fix commit 124(M). The function associated with the function name 125 may include multiple versions 126(1) to 126(P), with each version 126 having a different set of code. The fix commit 124(M) may address a vulnerability 127 included in one or more of the versions 126 of the function name 125). As per claims 7 and 14: Plate discloses the computerized method of claim 1, comprising displaying an alert on a graphical user interface (GUI) of a computer system, the alert describing the flagged one or more first party libraries (Paragraph 49; vulnerability alerting system). Relevant Prior Art References The following prior art is cited as being of interest to the claimed invention but has not been applied in any of the current rejections. Neystadt et al.- US Patent Publication 2020/0117808- the prior art teaches techniques for assess the vulnerability of one or more system devices. Nelson et al.- US Patent Pub. 2023/0097733 - the prior art teaches techniques for automatically identify types and status of vulnerabilities in identified software. Gottschlich et al.- US Patent Pub. 2021/0073391 - the prior art teaches techniques for identifying a vulnerability in the first representation of the algorithm. DiValentin et al.- US Patent Pub. 2024/0330484 - the prior art teaches techniques for identify changes to a third-party library after a vulnerability patch occurs. Conclusion THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action. Contact Information Any inquiry concerning this communication or earlier communications from the examiner should be directed to ANTHONY D BROWN whose telephone number is (571)270-1472. The examiner can normally be reached 730-330pm. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Linglan Edwards can be reached at 5712705440. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /ANTHONY D BROWN/Primary Examiner, Art Unit 2408
Read full office action

Prosecution Timeline

Mar 03, 2025
Application Filed
May 14, 2026
Non-Final Rejection mailed — §102
Aug 13, 2026
Response Filed
Oct 01, 2026
Final Rejection mailed — §102
Oct 23, 2026
Interview Requested
Nov 05, 2026
Applicant Interview (Telephonic)
Nov 09, 2026
Examiner Interview Summary

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12786240
PEER-TO-PEER NETWORK ROUTING BASED ON NETWORK DEVICE SECURITY CAPABILITIES
2y 4m to grant Granted Nov 03, 2026
Patent 12785972
SYSTEMS AND METHODS FOR IMPLEMENTING COMPUTER TRANSMISSION SECURITY PROTOCOL
1y 2m to grant Granted Nov 03, 2026
Patent 12769819
METHOD, APPARATUS AND COMPUTER PROGRAM
2y 4m to grant Granted Oct 20, 2026
Patent 12764150
CONDITIONAL EGRESS IP ADDRESS ASSIGNMENT AND SCORING FOR DELIVERY OF LOCALIZED CONTENT
2y 0m to grant Granted Oct 13, 2026
Patent 12762287
DATA PROCESSING METHOD AND APPARATUS BASED ON HIERARCHICAL CHAIN NETWORK
1y 9m to grant Granted Oct 13, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

3-4
Expected OA Rounds
86%
Grant Probability
99%
With Interview (+15.0%)
Moderate
PTA Risk
Based on 878 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month