Trust in Motion: Capturing Trust Ascendancy in
Open-Source Projects using Hybrid AI
Huascar Sanchez
Computer Science Laboratory
SRI International
huascar.sanchez@sri.com
Briland Hitaj
Computer Science Laboratory
SRI International
briland.hitaj@sri.com
Abstract—Open-source is frequently described as a driver for
unprecedented communication and collaboration, and the process
works best when projects support teamwork. Yet, open-source
cooperation processes in no way protect project contributors from
considerations of trust, power, and influence. Indeed, achieving
the level of trust necessary to contribute to a project and thus
influence its direction is a constant process of change, and
developers take many different routes over many communication
channels to achieve it. We refer to this process of influence-
seeking and trust-building as trust ascendancy.
This paper describes a methodology for understanding the
notion of trust ascendancy and introduces the capabilities that are
needed to localize trust ascendancy operations happening over
open-source projects. Much of the prior work in understanding
trust in open-source software development has focused on a static
view of the problem using different forms of quantity measures.
However, trust ascendancy is not static, but rather adapts to
changes in the open-source ecosystem in response to new input.
This paper is the first attempt to articulate and study these signals
from a dynamic view of the problem. In that respect, we identify
related work that may help illuminate research challenges,
implementation tradeoffs, and complementary solutions. Our
preliminary results show the effectiveness of our method at cap-
turing the trust ascendancy developed by individuals involved in a
well-documented 2020 social engineering attack. Our future plans
highlight research challenges and encourage cross-disciplinary
collaboration to create more automated, accurate, and efficient
ways to model and then track trust ascendancy in open-source
projects.
Index Terms—trust ascendancy modeling, dynamic developer
activity embeddings, influence pathway trajectories
I. INTRODUCTION
Achieving the level of trust necessary to contribute to a
project is a ubiquitous construct of how open-source software
development works [30], [35] and one of the most prevalent
objectives [26] in the general developer population in social
coding platforms like GitHub and Stack Overflow. Achieving
this trust is a dynamic process of change [11] that is inherently
political [13], and developers take many different routes over
many communication channels to influence its formation [2],
[9], [18], [35], [37]. We refer to this process of influence-
seeking and trust-building as trust ascendancy. Much of the
This material is based upon work supported by the Defense Advanced
Research Projects Agency (DARPA) under Contract No. HR00112190086.
Any opinions, findings, and conclusions or recommendations expressed in this
material are those of the author(s) and do not necessarily reflect the views of
the United States Government or DARPA.
prior work in understanding trust and its ascendancy in open-
source projects has focused on a static view of the problem
using scale measurements (e.g., [3], [15], [34], [38]). However,
trust ascendancy is not static. Instead, it adapts to changes
in the ecosystem in response to developer role changes, new
functionality, new technologies, and so on. Automatically
tracking this socio-technically stimulated dynamism thus re-
quires dynamic developer behavior models. This paper is a
first attempt to articulate and study this issue.
We consider the problem of capturing the motion dynamics
of trust ascendancy inside open-source software (OSS) projects
using dynamic developer activity models. These motion dy-
namics are reflected in the way trust is periodically developed
inside projects in response to either socio-technical stimuli
(e.g., social influence, role changes, code contributions) or
to periodic changes in the context of individual activities,
such as reporting a bug, that are intended to help potential
contributors build a reputation and eventually become project
committers (see the case study of a “successful socialization”
in Ducheneaut [13]). Understanding the context in which
actions are performed as well as tracking when (e.g., time of
day) this context changes can give us a global picture of the
influence pathways formed inside a project. Here, an influence
pathway is a potential conduit for influence to flow inside a
project and a schedule. The context of an activity embodies the
semantic associations between the activity and other activities
that were performed around the same schedule.
Arguably, influence is the main driver for building trust
inside networked social environments [37] like OSS projects.
The structure of these networks is usually “black-boxed,” and
to exert any influence in them, potential contributors need to
progressively make this network structure more visible [13].
A goal of the current effort is to bridge the gap mentioned
earlier, namely, that research on understanding trust and its
ascendancy tends to be based on static accounts. Consistent
with this goal, we introduce a hybrid approach that combines
the strength of unsupervised machine learning with the flexi-
bility of self-supervised machine learning, and generalize it to
sequential data collected from real-world software projects.
This work complements existing work by providing better
mapping and understanding of the multiple influence pathways
taken by developers to progressively open this “black-box,”
thereby enabling them to contribute to the project.
1
arXiv:2210.02656v2 [cs.SE] 10 Oct 2022