Purpose Detailed data comparing the biodistribution of PSMA radioligands is still scarce, raising concerns regarding the comparability of different compounds. We investigated differences in normal-organ biodistribution and uptake variability between the two most commonly PSMA tracers in clinical use, 68 Ga-PSMA-11 and 18 F-DCFPyL. Methods This retrospective analysis included 34 patients with low tumor burden referred for PET/CT imaging with 68 Ga-PSMA-11 and subsequently 18 F-DCFPyL. Images were acquired with 4 cross-calibrated PET/CT systems. Volumes of interest were placed on major salivary and lacrimal glands, liver, spleen, duodenum, kidneys, bladder, blood-pool and muscle. Normal-organ biodistribution of both tracers was then quantified as SUV peak and compared using paired tests, linear regression and Bland-Altman analysis. Between-patient variability was also assessed. Clinical and protocol variables were investigated for possible interference. Results For both tracers the highest uptake was found in the kidneys and bladder and low background activity was noted across all scans. In the quantitative analysis there was significantly higher uptake of 68 Ga-PSMA-11 in the kidneys, spleen and major salivary glands ( p <  0.001), while the liver exhibited slightly higher 18 F-DCFPyL uptake ( p = 0.001, mean bias 0.79 ± 1.30). The lowest solid-organ uptake variability was found in the liver (COV 21.9% for 68 Ga-PSMA-11, 22.5% for 18 F-DCFPyL). There was a weak correlation between 18 F-DCFPyL uptake time and liver SUV peak (r = 0.488, p = 0.003) and, accordingly, patients scanned at later time-points had a larger mean bias between the two tracers’ liver uptake values (0.05 vs 1.46, p = 0.001). Conclusion Normal tissue biodistribution patterns of 68 Ga-PSMA-11 and 18 F-DCFPyL were similar, despite subtle differences in quantitative values. Liver uptake showed an acceptable intra-patient agreement and low inter-patient variability between the two tracers, allowing its use as a reference organ for thresholding scans in the qualitative comparison of PSMA expression using these different tracers. Electronic supplementary material The online version of this article (10.1186/s40644-019-0211-y) contains supplementary material, which is available to authorized users.

No abstract

No abstract

The large amount of third-party packages available in fast-moving software ecosystems, such as Node.js/npm, enables attackers to compromise applications by pushing malicious updates to their package dependencies. Studying the npm repository, we observed that many packages in the npm repository that are used in Node.js applications perform only simple computations and do not need access to filesystem or network APIs. This offers the opportunity to enforce least-privilege design per package, protecting applications and package dependencies from malicious updates. We propose a lightweight permission system that protects Node.js applications by enforcing package permissions at runtime. We discuss the design space of solutions and show that our system makes a large number of packages much harder to be exploited, almost for free.

After the start of Lu-DOTA-TATE all patients achieved hypoglycaemia symptomatic control and had evident improvement of their quality of life. Three patients showed imagiological improvement suggesting reduced tumour load.

Transparent environments and social-coding platforms as GitHub help developers to stay abreast of changes during the development and maintenance phase of a project. Especially, notification feeds can help developers to learn about relevant changes in other projects. Unfortunately, transparent environments can quickly overwhelm developers with too many notifications, such that they lose the important ones in a sea of noise. Complementing existing prioritization and filtering strategies based on binary compatibility and code ownership, we develop an anomaly detection mechanism to identify unusual commits in a repository, which stand out with respect to other changes in the same repository or by the same developer. Among others, we detect exceptionally large commits, commits at unusual times, and commits touching rarely changed file types given the characteristics of a particular repository or developer. We automatically flag unusual commits on GitHub through a browser plug-in. In an interactive survey with 173 active GitHub users, rating commits in a project of their interest, we found that, although our unusual score is only a weak predictor of whether developers want to be notified about a commit, information about unusual characteristics of a commit changes how developers regard commits. Our anomaly detection mechanism is a building block for scaling transparent environments. KEYWORDSanomaly detection, information overload, notification feeds, software ecosystems, transparent environments INTRODUCTIONCollaborative development in open source, software ecosystems, and also industrial software systems relies increasingly on decentralized decision making. 1-4 Interdependent components evolve independently and often with little explicit collaboration. Backward-incompatible changes that break modularity and produce rippling effects on downstream components are often necessary to avoid opportunity costs (not fixing mistakes, stifling change in the face of evolving requirements) and common in practice. [5][6][7][8][9][10][11][12][13][14][15] In addition, components may change to add new functionality that developers might want to adopt. Identifying relevant changes and reacting to them if needed can create a significant burden on developers during maintenance. 10,[15][16][17][18][19][20] Seeds of a solution can be found in today's transparent environments or social-coding platforms such as GitHub, LaunchPad, and Bitbucket. These environments provide mechanisms for notification and exploration, that help developers to stay abreast of activities across collections of projects without central planning. 21,22 For example, on GitHub, developers can watch projects and receive a notification feed of activities in watched projects, such as push events or bug reports. These tools work well at small scales but break down for large projects where imprecise and insufficiently rich notification mechanisms lead to information overload from notification cluttering. By inspecting publicly available events on GitHub, we found t...

Preprocessors support the diversification of software products with #ifdefs, but also require additional effort from developers to maintain and understand variable code. We conjecture that #ifdefs cause developers to produce more vulnerable code because they are required to reason about multiple features simultaneously and maintain complex mental models of dependencies of configurable code.We extracted a variational call graph across all configurations of the Linux kernel, and used configuration complexity metrics to compare vulnerable and non-vulnerable functions considering their vulnerability history. Our goal was to learn about whether we can observe a measurable influence of configuration complexity on the occurrence of vulnerabilities.Our results suggest, among others, that vulnerable functions have higher variability than non-vulnerable ones and are also constrained by fewer configuration options. This suggests that developers are inclined to notice functions appear in frequently-compiled product variants. We aim to raise developers' awareness to address variability more systematically, since configuration complexity is an important, but often ignored aspect of software product lines.

Linezolid has been used in the treatment of multidrug-resistant/extensively drug-resistant tuberculosis in adults with encouraging results, however experience in children is scarce. We describe our experience with the use of linezolid as part of a multidrug regimen in the treatment of 4 patients who had persistent positive cultures, despite prolonged combined therapy.