Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page
Demo Data from EDBT 2026 / reviewers in the wild / expert

Rumen Paletov

dblp:220/9217 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2018
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Network and information security
1 paper
Systems and software security · 100%
Software engineering, system software, and programming languages
1 paper
Software maintenance and evolution · 100%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Systems and software security › vulnerability analysis
API misuse detection		 0.312018
Inferring crypto API rules from code changes · PLDI 2018
Systems and software security › software vulnerability
cryptographic API misuse		 0.312018
Inferring crypto API rules from code changes · PLDI 2018
Software maintenance and evolution
code change analysis		 0.312018
Inferring crypto API rules from code changes · PLDI 2018
YearPublicationVenuePosition
2018 Inferring crypto API rules from code changes
abstract
Creating and maintaining an up-to-date set of security rules that match misuses of crypto APIs is challenging, as crypto APIs constantly evolve over time with new cryptographic primitives and settings, making existing ones obsolete.
Rumen Paletov, Petar Tsankov, Veselin Raychev, Martin T. Vechev
 PLDI1