Kaka.Du [kakadu]

I don't see any security issues with the code - from a quick visual once-over.
Drupal code style conventions prefers the braces in a different place, so it's be cool if that was tidied up. Running the code through coder.module would be a nice start. Clean code style otherwise.

Using t() around your strings, and l() around the links (instead of "a href=...") is recommended.
You might want to put that display routine into a theme function for better formatting control.

I'm not sure I understand the purpose of the module, but I don't think there is a direct cross-over with anything already out there.

I am changing the status of the report as for previous comment.

@dman: if you want the OP changes something in the code, then you should change the status to needs work. Thanks for helping in reviewing the code; any help is well appreciated, and it makes the all CVS application approval more democratic. Having a single person who reviews the code doesn't assure a plurality of point of view.

@Kaka.Du: Remember to change the status, when you upload new code.

As I understand it, 100% strict code style is not a limiting prerequisite for CVS clearance. It's just something that makes life much easier on the reviewers. What is important is that you know that the coding standards exist, and at least try to follow them when you can.
Now you've played with coder.module, I think that requirement is passed.

Anyway,

for($i=0; $i<$limite; $i++) {

Becomes:

for ($i=0; $i<$limite; $i++) {

and, oh dear..
Right... t() is used around strings of text that may need translating. It's not required around every string! t(' .') is not helpful :-)
If appropriate, leave the html outside of the t() too, although embedding a little HTML doesn't hurt.

$page_content.= t('< strong >'). $rs['items'][$i]['pubDate'].t(' ·').l($rs['items'][$i]['title'], $rs['items'][$i]['link'], array('attributes' => array('target' => '_blank'))).t('
');

.. that line was fine before, without the t(). There is nothing a translator can do with that line. Just get some spaces around the .
I just updated the guidelines on using t().

Based on the t() confusion, I'd suggest that code gets fixed as 'needs work', but as far as an application for CVS access goes, I think that's enough initiation. :-)
I wouldn't want to hold an application up for code convention whitespace issues, especially now you have started to use coder.module.

ps - if you wanted to use t(), I'd probably refactor it a bit like:

$item = $rs['items'][$i];
$link = l($item['title'], $item['link'], array('attributes' => array('target' => '_blank'));
$page_content .= t('Date:<strong>@date</strong> Link: !link', array('@date' => $item['pubDate'], '!link' => $link));

Long lines are a pain, there is no harm in breaking things down into short bits with nice labels. (This is opinion-advice, not strict policy)

I only added the "Date,Link" text in there so that t() had something to do to demonstrate.
Without it,

$page_content .= "<strong>{$item['pubDate']}</strong> $link";

Would be fine too.

There have not been replies from the OP in the past 7 days. I am marking this report as won't fix.

Almost a month is passed, and no news have been heard from the OP. I am marking this report as won't fix.