Abstract: A computer implemented method includes determining a first level of risk based on a context of source code as stored. A second level of risk is determined based on a change history of the source code. A third level of risk is determined by assessing a nature of changes to the source code. The first, second, and third levels of risk are combined to generate an indication of trust in the source code.

Abstract: A computer implemented method includes detecting a current workstream of development tasks associated with a software development project. An activity attempting to access a resource is detected. Access rights to the resource are determined with respect to the activity as a function of the current workstream of development tasks. Access to the resource is controlled in accordance with the access rights.

Abstract: A computer implemented method includes detecting a current workstream of development tasks associated with a software development project. An activity attempting to access a resource is detected. Access rights to the resource are determined with respect to the activity as a function of the current workstream of development tasks. Access to the resource is controlled in accordance with the access rights.

Abstract: A computer implemented method includes determining a first level of risk based on a context of source code as stored. A second level of risk is determined based on a change history of the source code. A third level of risk is determined by assessing a nature of changes to the source code. The first, second, and third levels of risk are combined to generate an indication of trust in the source code.

Abstract: Embodiments relate to incorporating supplemental information into a code editor's editing view that may make the code more understandable to those not familiar or comfortable with the code. The editor receives adornments that may be translations or semantic equivalents of constructs already in the code. The editor adds the adornments to an editing view for editing the source code. The adornments are inserted into lines of the source code displayed in the editing view and have some of the appearance of the source code in the editing view. The adornments are passive with respect to the source code; they are not necessarily compiled or saved. The adornments may be tokens provided by a compiler and/or an integrated development environment. The editor may apply heuristics or rules to determine which adornments are to be used and where they will be inserted.

Abstract: Embodiments relate to incorporating supplemental information into a code editor's editing view that may make the code more understandable to those not familiar or comfortable with the code. The editor receives adornments that may be translations or semantic equivalents of constructs already in the code. The editor adds the adornments to an editing view for editing the source code. The adornments are inserted into lines of the source code displayed in the editing view and have some of the appearance of the source code in the editing view. The adornments are passive with respect to the source code; they are not necessarily compiled or saved. The adornments may be tokens provided by a compiler and/or an integrated development environment. The editor may apply heuristics or rules to determine which adornments are to be used and where they will be inserted.

Abstract: Embodiments relate to incorporating supplemental information into a code editor's editing view that may make the code more understandable to those not familiar or comfortable with the code. The editor receives adornments that may be translations or semantic equivalents of constructs already in the code. The editor adds the adornments to an editing view for editing the source code. The adornments are inserted into lines of the source code displayed in the editing view and have some of the appearance of the source code in the editing view. The adornments are passive with respect to the source code; they are not necessarily compiled or saved. The adornments may be tokens provided by a compiler and/or an integrated development environment. The editor may apply heuristics or rules to determine which adornments are to be used and where they will be inserted.

Abstract: Embodiments relate to incorporating supplemental information into a code editor's editing view that may make the code more understandable to those not familiar or comfortable with the code. The editor receives adornments that may be translations or semantic equivalents of constructs already in the code. The editor adds the adornments to an editing view for editing the source code. The adornments are inserted into lines of the source code displayed in the editing view and have some of the appearance of the source code in the editing view. The adornments are passive with respect to the source code; they are not necessarily compiled or saved. The adornments may be tokens provided by a compiler and/or an integrated development environment. The editor may apply heuristics or rules to determine which adornments are to be used and where they will be inserted.