Abstract: The present disclosure pertains to an emergency response vehicle designed for human-powered operation with the versatility to function both indoors and outdoors. The vehicle is particularly suited for deployment in high-risk areas to offer protection in emergency situations. It features a manually operable control system that allows for intuitive navigation, akin to the operation of a standard bicycle, making it accessible for users of all competencies. Emphasized within the vehicle's design is an integrated defense mechanism forged with bullet-resistant materials, aimed at safeguarding the operator amidst harmful scenarios, while the vehicle itself acts as a mobile protective barrier. Additionally, the vehicle is equipped with a built-in offense system incorporating multiple non-lethal deterrents, providing a range of defensive options against potential threats.

Abstract: The disclosure provides a method for querying data across a plurality of distributed databases. The method includes receiving a query at a local coordinator of a local database cluster. The method further includes sending the query to a remote coordinator of a remote database cluster. The method further includes retrieving, by each local segment of a plurality of local segments of the local database cluster, data responsive to the query from corresponding one or more remote segments of the remote database cluster associated with the local segment. The method further includes sending a response to the query based on the data responsive to the query from each of the corresponding one or more remote segments.

Abstract: Devices, systems, and methods are provided for opening a coconut. A coconut opening device or system may include a piercing component to pierce a coconut; an adjustable component to move the piercing component vertically with respect to the ground toward and away from a coconut based on a received user input; and a coconut holding component arranged below the piercing component to secure the coconut while the coconut is pierced by the piercing component.

Abstract: This application describes techniques for providing computer vision for manual services. In some instances, a remote system may determine that a current time is within a threshold period of time of a scheduled service and, based on the determination, send a first message requesting image data to a camera apparatus located within an environment. After sending the first message, the remote system may receive image data associated with the environment from the camera apparatus and use the image to detect an object within the environment. The remote system can then send a second message to a device of a guest and a third message to a device of a user, where each of the second message and the third message indicates that the object is within the environment. In some instances, the object can include an animal while in some instances, the object can include a person.

Abstract: Techniques are generally described for scene change detection. A first and second histogram representing frames of a video may be received. A Euclidean distance between the first and second histogram may be determined. A third histogram of a third frame may be received. Values of the third histogram may be compared to corresponding values of a background model of the environment. A fourth frame and a fifth frame of image data of the video may be received. A flow value between a first block of pixels of the fourth frame and a corresponding second block of pixels of the fifth frame may be determined. The flow value may be determined based on a motion vector and a sum of absolute differences between the first and second block. A portion of the video may be streamed to a remote computing device if the flow value exceeds a threshold value.

Abstract: This application describes techniques for providing computer vision for manual services. In some instances, a remote system may determine that a current time is within a threshold period of time of a scheduled service and, based on the determination, send a first message requesting image data to a camera apparatus located within an environment. After sending the first message, the remote system may receive image data associated with the environment from the camera apparatus and use the image to detect an object within the environment. The remote system can then send a second message to a device of a guest and a third message to a device of a user, where each of the second message and the third message indicates that the object is within the environment. In some instances, the object can include an animal while in some instances, the object can include a person.

Abstract: This application describes techniques for providing computer vision-based surveillance of in-home services. In some instances, a remote system may authenticate a guest at an environment using data that the remote system receives from a camera apparatus. To authenticate the guest, the remote system can determine that an identification of the guest matches an identification of a worker associated with a scheduled service at the environment. When the scheduled service includes an in-home delivery, the remote system can further determine that a package in possession of the guest matches an item for the scheduled in-home delivery. In some instances, after the guest enters the environment, the remote system can further monitor the environment to ensure that the guest stays within a designated location of the environment. The remote system can further send a message to an electronic device when the guest is outside of the designated location.

Abstract: During runtime of the software application, the runtime analysis framework may assign input tags to objects associated with the user requests. The input tags may identify the requests as potentially malicious and carry a security risk. The RTA framework then may assign sanitization tags to the objects identifying security checks performed on the objects during runtime. The RTA framework identifies output responses to the user requests that include the objects and compares the input tags assigned to the objects with any sanitization tags assigned to the objects. The RTA framework may identify the software application as susceptible to a security vulnerability when the input tags for the objects do not include corresponding sanitization tags.

Abstract: A runtime analysis framework (RTA) stores a hierarchical list of input tags and a hierarchical list of output tags. The RTA stores defined vulnerabilities that include associated input tags and output tags. During runtime the software application may receive a request from a user system. The RTA assigns an input tag from the hierarchical list of input tags to an object associated with the request and assigns an output tag from the hierarchical list of output tags to a method generating a response to the request. The RTA identifies one of the defined vulnerabilities as a potential vulnerability if the assigned output tag and output tag associated the potential vulnerability are in a same subtree of the hierarchical list of output tags and the assigned input tag and the input tag associated with the potential vulnerability are in a same subtree of the hierarchical list of input tags.

Abstract: During runtime of the software application, the runtime analysis framework may assign input tags to objects associated with the user requests. The input tags may identify the requests as potentially malicious and carry a security risk. The RTA framework then may assign sanitization tags to the objects identifying security checks performed on the objects during runtime. The RTA framework identifies output responses to the user requests that include the objects and compares the input tags assigned to the objects with any sanitization tags assigned to the objects. The RTA framework may identify the software application as susceptible to a security vulnerability when the input tags for the objects do not include corresponding sanitization tags.

Abstract: During runtime of the software application, the runtime analysis framework may assign input tags to objects associated with the user requests. The input tags may identify the requests as potentially malicious and carry a security risk. The RTA framework then may assign sanitization tags to the objects identifying security checks performed on the objects during runtime. The RTA framework identifies output responses to the user requests that include the objects and compares the input tags assigned to the objects with any sanitization tags assigned to the objects. The RTA framework may identify the software application as susceptible to a security vulnerability when the input tags for the objects do not include corresponding sanitization tags.

Abstract: A runtime analysis framework (RTA) stores a hierarchical list of input tags and a hierarchical list of output tags. The RTA stores defined vulnerabilities that include associated input tags and output tags. During runtime the software application may receive a request from a user system. The RTA assigns an input tag from the hierarchical list of input tags to an object associated with the request and assigns an output tag from the hierarchical list of output tags to a method generating a response to the request. The RTA identifies one of the defined vulnerabilities as a potential vulnerability if the assigned output tag and output tag associated the potential vulnerability are in a same subtree of the hierarchical list of output tags and the assigned input tag and the input tag associated with the potential vulnerability are in a same subtree of the hierarchical list of input tags.

Abstract: During runtime of the software application, the runtime analysis framework may assign input tags to objects associated with the user requests. The input tags may identify the requests as potentially malicious and carry a security risk. The RTA framework then may assign sanitization tags to the objects identifying security checks performed on the objects during runtime. The RTA framework identifies output responses to the user requests that include the objects and compares the input tags assigned to the objects with any sanitization tags assigned to the objects. The RTA framework may identify the software application as susceptible to a security vulnerability when the input tags for the objects do not include corresponding sanitization tags.

Abstract: Data source information is recorded into a source tracking object embedded in a wrapper object pointing to a data object from the data source. Tracking event information is recorded into a flow tracking object embedded in a wrapper object copy as the tracking event processes the wrapper object copy. Other tracking event information is recorded into another flow tracking object embedded in another wrapper object as the other tracking event processes the other wrapper object. The flow tracking object is associated with the other flow tracking object in response to a field retrieval of the wrapper object copy from the other wrapper object. The wrapper object copy is output to a data sink. Data sink information is recorded into a sink tracking object embedded in the wrapper object copy. The tracking objects are output as dynamic analysis of dataflow in the application program.

Abstract: Systems and methods are provided for dynamic analysis wrapper objects for application dataflow. A system creates a wrapper object that points to a data object received from a data source, creates a source tracking object for the wrapper object, and records information associated with the data source into the source tracking object. The system creates a copy of the wrapper object for a tracking event in an application program, creates a flow tracking object for the tracking event, and records information associated with the tracking event into the flow tracking object as the tracking event processes the copy of the wrapper object. The system outputs the copy of the wrapper object to a data sink for the application program, creates a sink tracking object for the data sink, and records information associated with the data sink into the sink tracking object.

Abstract: Bytecode is injected to create a source tracking object for a data object received from a data source and to record information associated with the data source into the source tracking object. Bytecode is injected to create a copy of the data object for a tracking event in an application program, to create a flow tracking object for the tracking event, and to record information associated with the tracking event into the flow tracking object as the tracking event processes the copy of the data object. Bytecode is injected to create a sink tracking object for outputting the copy of the data object to a data sink and to record information associated with the data sink into the sink tracking object. Bytecode is injected to output the source tracking object, the flow tracking object, and the sink tracking object as dynamic analysis of dataflow in the application program.

Abstract: Systems and methods are provided for dynamic analysis tracking objects for application dataflow. A system receives a data object from a data source, creates a source tracking object for the data object, and records information associated with the data source into the source tracking object. The system creates a copy of the data object for a tracking event in the application program, creates a flow tracking object for the tracking event, and records information associated with the tracking event into the flow tracking object as the tracking event processes the copy of the data object. The system outputs the copy of the data object to a data sink, creates a sink tracking object for the data sink, and records information associated with the data sink into the sink tracking object. The system outputs the source tracking object, the flow tracking object, and the sink tracking object as dynamic analysis of dataflow in the application program.

Abstract: An interpreter is modified to create a source tracking object for a data object received from a data source and to record information associated with the data source into the source tracking object. The interpreter is modified to create a copy of the data object for a tracking event in an application program, to create a flow tracking object for the tracking event, and to record information associated with the tracking event into the flow tracking object as the tracking event processes the copy of the data object. The interpreter is modified to create a sink tracking object for outputting the copy of the data object to a data sink and to record information associated with the data sink into the sink tracking object. The source tracking object, the flow tracking object, and the sink tracking object are output as dynamic analysis of dataflow in the application program.

Abstract: An interpreter is modified to create a source tracking object for a data object received from a data source and to record information associated with the data source into the source tracking object. The interpreter is modified to create a copy of the data object for a tracking event in an application program, to create a flow tracking object for the tracking event, and to record information associated with the tracking event into the flow tracking object as the tracking event processes the copy of the data object. The interpreter is modified to create a sink tracking object for outputting the copy of the data object to a data sink and to record information associated with the data sink into the sink tracking object. The source tracking object, the flow tracking object, and the sink tracking object are output as dynamic analysis of dataflow in the application program.

Abstract: Systems and methods are provided for dynamic analysis tracking objects for application dataflow. A system receives a data object from a data source, creates a source tracking object for the data object, and records information associated with the data source into the source tracking object. The system creates a copy of the data object for a tracking event in the application program, creates a flow tracking object for the tracking event, and records information associated with the tracking event into the flow tracking object as the tracking event processes the copy of the data object. The system outputs the copy of the data object to a data sink, creates a sink tracking object for the data sink, and records information associated with the data sink into the sink tracking object. The system outputs the source tracking object, the flow tracking object, and the sink tracking object as dynamic analysis of dataflow in the application program.