Safari 7.0.5 on 10.9.4 fails to check code-signing
I don't think this is dangerous. I don't think you need to worry about it.

The affected files are just pairs of strings and the translated version for a particular language. The InfoPlist.strings file contains the file descriptions that appear in the Finder (and other places I assume) for the Document Types that Safari supports, for example "HTML document" and "CSS style sheet". The ServicesMenu.strings contains a similar short list of the Services provided by Safari, for example "Add to Reading List". The two files that are being flagged as modified are a bit boring as they are providing English translations for strings that are already in English. If you check the same files in another language folder within the Safari bundle, like for example French the concept is clearer.

&lt;key&gt;Web internet location&lt;/key&gt;
&lt;string&gt;Adresse Internet du Web&lt;/string&gt;
&lt;key&gt;Web site URL&lt;/key&gt;
&lt;string&gt;Adresse URL du site web&lt;/string&gt;
&lt;key&gt;Web site location&lt;/key&gt;
&lt;string&gt;Adresse du site web&lt;/string&gt;
&lt;key&gt;Windows icon image&lt;/key&gt;
&lt;string&gt;Fenêtres icône image&lt;/string&gt;


Within the thread discussing 1Password it doesn't appear that the modification was caused by 1Password. In fact it was initially suspected to be the reverse, the discussion in that thread was about whether the modifications were causing a problem with 1Password because someone was having trouble running it. In the end it turned out that the problem with 1Password was caused by Sophos. The modified Safari files had nothing to do with it.

For what it's worth I get the same errors when I run codesign against Safari on both my Macs. I tried reinstalling the latest OS X update (which includes Safari 7.0.5) but that made no difference. Even tried repairing permissions (which funnily enough did make one correction to a file in the Safari bundle) but unfortunately didn't resolve this issue.

Unless you have a problem running Safari or running extensions within Safari, I wouldn't worry about this.