---
title: "File Safer malware scan"
slug: "sourcecommit-use-filesafer"
tags: ["SourceCommit", "File Safer"]
updated: 2026-09-17T09:17:50Z
published: 2026-09-17T09:17:50Z
canonical: "guide.ncloud-docs.com/sourcecommit-use-filesafer"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# File Safer malware scan

Available in Classic and VPC

If you selected the File Safer integration option when creating a SourceCommit repository, you can use the malware detection feature provided by File Safer. Check the malware of files in the repository using the File Filter feature of File Safer.

              Note

              

- For more information on how to create SourceCommit, see [Getting started with SourceCommit](/docs/en/sourcecommit-start).
- For more information on various features of File Safer, see [File Safer user guide](/docs/en/security-security-6-2).

## Check scan status

To check the File Safer malware scan status, follow these steps:

1. From the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Developer Tools** > **SourceCommit**.
2. Select a repository from the SourceCommit page and then click the **[Go to code]** button.
  - You can also click the repository name from the repository list.
3. Click the **[Commit]** tab of the Repository's detailed feature page, and then check the **FILE SAFER** item displayed on the right side of the list.  

![sourcecommit-use_fs1_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/sourcecommit-use_fs1_en.png?sv=2026-02-06&spr=https&st=2026-11-14T04%3A28%3A09Z&se=2026-11-14T05%3A28%3A09Z&sr=c&sp=r&sig=wpvx%2BB0Mq33MwCbnnYS55dYkzgms9OQTPGndIBF6vLI%3D)
  - The following describes the statuses shown in the **FILE SAFER** item.
    - **Not scanned**: File Safer scanning is not conducted
    - **Scanning**: scanning of File Safer in progress
    - **Scanned**: File Safer scan completed

## Request scan

To request File Safer malware scan for the commit, follow these steps:

              Note

              

- You can scan the script and binary files of up to 10 MB by requesting File Safer scan.
- Scan target extensions: `bat`, `cmd`, `vbs`, `vbe`, `js`, `jse`, `wsf`, `wsh`, `html`, `htm`, `hta`, `jsp`, `php`, `cgi`, `ahk`, `au3`, `py`, `lsp`, `fas`, `ps`, `eps`, `gsf`, `ps1`, `sh`, `exe`, `dll`, `com`, `so`, `zip`, `tar`, `gz`, `tgz`, `rar`, `xz`, `7z`
- You can change the scan target extensions later.

1. From the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Developer Tools** > **SourceCommit**.
2. Select a repository from the SourceCommit page and then click the **[Go to code]** button.
  - You can also click the repository name from the repository list.
3. From the Repository's detailed feature page, click the **[Commit]** tab.
4. Find a commit shown as **Not scanned** in the **FILE SAFER** item from the commit list, and then click ![i-sourcecommit-filesafer.png](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/i-sourcecommit-filesafer.png?sv=2026-02-06&spr=https&st=2026-11-14T04%3A28%3A09Z&se=2026-11-14T05%3A28%3A09Z&sr=c&sp=r&sig=wpvx%2BB0Mq33MwCbnnYS55dYkzgms9OQTPGndIBF6vLI%3D).
5. Select the **Set scanning target** and **Set scanning option** items in the **File Safer scan** area of the File Safer result popup window, and then click the **[Request scanning]** button.  

![sourcecommit-use_fs2_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/sourcecommit-use_fs2_en.png?sv=2026-02-06&spr=https&st=2026-11-14T04%3A28%3A09Z&se=2026-11-14T05%3A28%3A09Z&sr=c&sp=r&sig=wpvx%2BB0Mq33MwCbnnYS55dYkzgms9OQTPGndIBF6vLI%3D)

## Check scan result

To complete the File Safer's malware scan and check the scan result, follow these steps:

              Note

              

- File Safer's scan result is provided based on the file's hash value, not the repository. So if there's a scan history for the file, the scan result is shown regardless of the repository's location.

1. From the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Developer Tools** > **SourceCommit**.
2. Select a repository from the SourceCommit page and then click the **[Go to code]** button.
  - You can also click the repository name from the repository list.
3. Click the **[Code]** tab of the Repository's detailed feature page, and then check the **FILE SAFER** item displayed on the right side of the list.  

![sourcecommit-use_fs3_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/sourcecommit-use_fs3_en.png?sv=2026-02-06&spr=https&st=2026-11-14T04%3A28%3A09Z&se=2026-11-14T05%3A28%3A09Z&sr=c&sp=r&sig=wpvx%2BB0Mq33MwCbnnYS55dYkzgms9OQTPGndIBF6vLI%3D)
  - The following describes the statuses shown in the **FILE SAFER** item.
    - **Safe**: safe file
    - **Suspected to be malicious**: detected malicious file
    - **Not scanned**: no File Safer scan history
    - **Scanning**: File Safer scanning in progress
    - **Not target**: not a target for File Safer scan