human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "do android taint analysis tools keep their promises"
  Abstract: In recent years, researchers have developed a number of tools to conduct taint analysis of Android applications. While all the respective papers aim at providing a thorough empirical evaluation, comparability is hindered by varying or unclear evaluation targets. Sometimes, the apps used for evaluation are not precisely described. In other cases, authors use an established benchmark but cover it only partially. In yet other cases, the evaluations differ in terms of the data leaks searched for, or lack a ground truth to compare against. All those limitations make it impossible to truly compare the tools based on those published evaluations. #R##N#We thus present ReproDroid, a framework allowing the accurate comparison of Android taint analysis tools. ReproDroid supports researchers in inferring the ground truth for data leaks in apps, in automatically applying tools to benchmarks, and in evaluating the obtained results. We use ReproDroid to comparatively evaluate on equal grounds the six prominent taint analysis tools Amandroid, DIALDroid, DidFail, DroidSafe, FlowDroid and IccTA. The results are largely positive although four tools violate some promises concerning features and accuracy. Finally, we contribute to the area of unbiased benchmarking with a new and improved version of the open test suite DroidBench.

Connected through hyperedge HE-1 (induced by source paper "are free android app security analysis tools effective in detecting known vulnerabilities"):
  with members:
    - "ghera a repository of android app vulnerability benchmarks"
    - "horndroid practical and sound static analysis of android applications by smt solving"
    - "an application package configuration approach to mitigating android ssl vulnerabilities"

Connected through hyperedge HE-2 (induced by source paper "sema extending and analyzing storyboards to develop secure android apps"):
  with members:
    - "web apis in android through the lens of security"
    - "are free android app security analysis tools effective in detecting known vulnerabilities"
    - "ghera a repository of android app vulnerability benchmarks"

Connected through hyperedge HE-3 (induced by source paper "web apis in android through the lens of security"):
  with members:
    - "security code smells in android icc"
    - "who you gonna call analyzing web requests in android applications"

Connected through hyperedge HE-4 (induced by source paper "configcrusher white box performance analysis for configurable systems"):
  with members:
    - "igen dynamic interaction inference for configurable software"
    - "test them all is it worth it assessing configuration sampling on the jhipster web development stack"
    - "self adaptive static analysis"
    - "an uncertainty aware approach to optimal configuration of stream processing systems"
    - "a comparison of 10 sampling algorithms for configurable systems"
    - "precise dynamic information flow for database backed applications"

Connected through hyperedge HE-5 (induced by source paper "benchpress analyzing android app vulnerability benchmark suites"):
  with members:
    - "are free android app security analysis tools effective in detecting known vulnerabilities"
    - "ghera a repository of android app vulnerability benchmarks"
    - "horndroid practical and sound static analysis of android applications by smt solving"
    - "beebs open benchmarks for energy measurements on embedded platforms"

Connected through hyperedge HE-6 (induced by source paper "sema a design methodology for building secure android apps"):
  with members:
    - "are free android app security analysis tools effective in detecting known vulnerabilities"
    - "ghera a repository of android app vulnerability benchmarks"
    - "model driven development of complex software a research roadmap"

Connected through hyperedge HE-7 (induced by source paper "mobile app analysis and instrumentation techniques reimagined with decree"):
  with members:
    - "empirically assessing opportunities for prefetching and caching in mobile apps"
    - "leveraging program analysis to reduce user perceived latency in mobile applications"
    - "dexpler converting android dalvik bytecode to jimple for static analysis with soot"

Connected through hyperedge HE-8 (induced by source paper "pointeval on the impact of pointer analysis frameworks"):
  with members:
    - "heap abstractions for static analysis"

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.SE(Software Engineering)