Compétences labarchive-integration Historique des audits
🔬

Historique des audits

labarchive-integration - 4 audits

Version de l’audit 4

Dernier Risque faible

Jan 17, 2026, 06:08 AM

All 275 static findings are false positives. Scanner triggered on markdown documentation (backtick syntax), security best practices (encrypt keyword), standard file operations (file existence checks), and legitimate API endpoints. Code review confirms no malicious patterns. This is legitimate LabArchives electronic lab notebook API integration.

9
Fichiers analysés
2,680
Lignes analysées
3
résultats
claude
Audité par
Aucun problème de sécurité trouvé

Version de l’audit 3

Risque faible

Jan 17, 2026, 06:08 AM

All 275 static findings are false positives. Scanner triggered on markdown documentation (backtick syntax), security best practices (encrypt keyword), standard file operations (file existence checks), and legitimate API endpoints. Code review confirms no malicious patterns. This is legitimate LabArchives electronic lab notebook API integration.

9
Fichiers analysés
2,680
Lignes analysées
3
résultats
claude
Audité par
Aucun problème de sécurité trouvé

Version de l’audit 2

Risque faible

Jan 12, 2026, 04:38 PM

The static analysis flagged numerous false positives. The 'external_commands' findings are markdown code blocks showing API URL patterns, not actual command execution. The 'weak cryptographic algorithm' findings reference MD5 in documentation examples, not actual implementation. This is a legitimate research tool for LabArchives API integration with no malicious intent detected.

7
Fichiers analysés
2,206
Lignes analysées
2
résultats
claude
Audité par
Aucun problème de sécurité trouvé

Version de l’audit 1

Risque faible

Jan 4, 2026, 04:43 PM

This is a legitimate LabArchives API integration skill for electronic lab notebooks. Scripts make documented API calls to LabArchives endpoints only. Credentials are stored in config.yaml with restrictive 600 file permissions. No credential harvesting, exfiltration, or unexpected network destinations detected.

10
Fichiers analysés
2,473
Lignes analysées
6
résultats
claude
Audité par
Problèmes à risque faible (2)
Credentials stored in local config file
The setup_config.py script collects API credentials (access_key_id, access_password, user_email, user_external_password) and stores them in config.yaml. While file permissions are set to 600 (user read/write only), sensitive credentials are written to disk. Location: scripts/setup_config.py:72-79 ```python def create_config_file(config_data, output_path='config.yaml'): with open(output_path, 'w') as f: yaml.dump(config_data, f, default_flow_style=False, sort_keys=False) os.chmod(output_path, 0o600) ``` Mitigation: The documentation recommends adding config.yaml to .gitignore and provides an environment variable alternative for credential storage.
Credentials transmitted in API requests
The entry_operations.py script sends access credentials (access_key_id, access_password) as form data in HTTP POST requests to upload attachments. Location: scripts/entry_operations.py:163-172 ```python data = { 'uid': uid, 'nbid': nbid, 'entry_id': entry_id, 'filename': file_path.name, 'access_key_id': config['access_key_id'], 'access_password': config['access_password'] } response = requests.post(url, files=files, data=data) ``` This is standard API authentication behavior but credentials transit through the network.