<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 21 May 2013 10:55:57 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Felix De Vliegher's Blog: Static analysis for PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/10856</guid>
      <link>http://www.phpdeveloper.org/news/10856</link>
      <description><![CDATA[<p>
On his blog recently <i>Felix De Vliegher</i> has <a href="http://felix.phpbelgium.be/blog/2008/08/14/static-analysis-for-php/">posted about work he's done</a> to gather some stats and great some data about how his PHP scripts are working based on a little <a href="http://en.wikipedia.org/wiki/Static_code_analysis">statistical analysis</a>.
</p>
<blockquote>
Lately I've been interested in applying <a href="http://en.wikipedia.org/wiki/Static_code_analysis">static analysis</a> to PHP projects. Static analysis is the process of analysing software code - in our case PHP source code -, without actually executing the (compiled) result of the source code you're analysing.
</blockquote>
<p>
He mentions some types of analysis and some of the tools that can be used to measure it. He also talks about issues it can help with (like the potential for harm if a part of code is changed) and a pointer to the <a href="http://pixybox.seclab.tuwien.ac.at/pixy/">Pixy</a> software he used to generate the statistics (and images like <a href="http://felix.phpbelgium.be/blog/wp-content/uploads/2008/08/callgraph.png">this</a>). 
</p>]]></description>
      <pubDate>Tue, 19 Aug 2008 11:16:18 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Greg Beaver's Blog: Quick review of Pixy vulnerability scanner for PEAR users]]></title>
      <guid>http://www.phpdeveloper.org/news/8111</guid>
      <link>http://www.phpdeveloper.org/news/8111</link>
      <description><![CDATA[<p>
<i>Greg Bever</i> has a <a href="http://greg.chiaraquartet.net/archives/178-quick-review-of-Pixy-vulnerability-scanner-for-PEAR-users.html">(very) quick post</a> about his experiences with the <a href="http://pixybox.seclab.tuwien.ac.at/pixy/index.php">Pixy XSS and SQLI Scanner</a> running against PEAR files.
</p>
<blockquote>
I tried out the Pixy XSS and SQLI Scanner (<a href="http://pixybox.seclab.tuwien.ac.at/pixy/index.php">http://pixybox.seclab.tuwien.ac.at/pixy/index.php</a>) on a few simple PEAR files.  On the first, I got a java exception, on the second it was unable to resolve the simplest of includes (no ability to resolve include_path). In short, the thing is useless for anything written using PEAR.  Fun!
</blockquote>
<p>
The Pixy XSS and SQLI Scanner is made to find SQL and XSS injection issues in scripts. It runs as a Java application and scans PHP4 source code to try to find problems. For more information on the scanner or to try it out for yourself, check out <a href="http://pixybox.seclab.tuwien.ac.at/pixy/index.php">the project's homepage</a> for documentation and downloads.
</p>]]></description>
      <pubDate>Mon, 25 Jun 2007 07:30:27 -0500</pubDate>
    </item>
  </channel>
</rss>
