You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the parser tries to filter out identifier references and only report declarations. In particular, identifiers are parsed from variable, function, method and class declarations (and more), and this is good because it captures names that originate from the package.
On the other hand, names of variables that are simply written to or read from are ignored, and calls to functions or methods are ignored since they must have been defined elsewhere. The downside of this is that there might be telltale ('suspicious') function calls which are often associated with obfuscated code, such as exec.
So it might make sense to include some level of referenced identifiers in the parser output too, with some extra metadata that can be used to distinguish between what's been declared in the file vs what was simply referenced.
The text was updated successfully, but these errors were encountered:
Currently, the parser tries to filter out identifier references and only report declarations. In particular, identifiers are parsed from variable, function, method and class declarations (and more), and this is good because it captures names that originate from the package.
On the other hand, names of variables that are simply written to or read from are ignored, and calls to functions or methods are ignored since they must have been defined elsewhere. The downside of this is that there might be telltale ('suspicious') function calls which are often associated with obfuscated code, such as
exec
.So it might make sense to include some level of referenced identifiers in the parser output too, with some extra metadata that can be used to distinguish between what's been declared in the file vs what was simply referenced.
The text was updated successfully, but these errors were encountered: