Meterian
  • Meterian
    • The Platform
    • SSO and MFA
    • Support
  • Codebase scanner
    • The Thin Client
      • How does the client work?
      • How does the client authenticate me?
      • How do I get the client?
      • What if I need a previous release?
      • Use the thin client on Windows
    • Using the client from your command line
      • Authorization in interactive mode
      • Interrupting the client
      • Example: running the client in interactive mode
    • Using the client in your CI/CD pipeline
      • Authorization in non-interactive mode
      • Providing the project branch
      • Concurrent mode
      • Two phases build
      • Controlling the exit code
      • Example: running the client in non-interactive mode
    • General operations
      • Running the analysis remotely
      • Interrupting the client
      • Generating a report
      • Forcing or avoiding specific scans
      • Excluding (and including) specific folders
      • Connecting through a proxy
    • System requirements
    • Command line parameters
      • General configuration
      • Overriding scores
      • Overriding scopes
      • Producing reports
      • Selecting scanners
      • Defining projects
      • Advanced options
        • Autofix
        • Pull Requests
      • System information
      • Specific controls
        • Maven specific controls
        • Dotnet specific controls
        • Npm/Yarn specific controls
        • Gradle specific controls
        • Ant/Ivy specific controls
    • The Dockerized Client
      • Basic usage
      • Advanced usage
        • Invoking via Docker
        • Platform-specific images
        • Usage on a CI/CD platform
        • Disable the client auto-update
      • Troubleshooting
        • Client auto update failure
        • Docker specifics
    • How scores work
    • Guide: your first scan!
      • Your first scan (java thin client)
      • Your first scan (dockerized client)
      • Your first scan (GitHub Action)
  • Scan behaviour matrix
  • THE METERIAN DASHBOARD
    • The Web Dashboard
      • Projects
      • Insights
      • Tokens
      • Badges
      • Policies
      • Tags
      • Teams
      • Configuration
        • Automatic Temporary Branches Clean-up
    • Advanced functionalities
      • Safe versions
      • Software Bill Of Materials (SBOM)
      • Auto-grouping
        • Domain auto-grouping
        • Github auto-grouping
      • How to set a vulnerability exclusion
        • From the report page
        • From the dashboard
        • The .meterian file
        • Generate the .meterian file
    • Troubleshooting
      • Login with credentials
  • Notifications
    • Sentinel
      • Notifications for Slack
      • Notifications for Email
    • Allerta
  • Github Badges
    • Introduction
    • Public repository
    • Private repository
  • ONLINE INTEGRATIONS
    • Introduction
    • GitHub Action
      • Using the Thin Client
      • Code scanning
    • Bitbucket Pipe
    • Azure DevOps Pipelines
  • Languages support
    • Introduction
    • C/C++
    • Clojure
    • Dart / Flutter
    • Elixir (erlang)
    • Golang
    • Java/Kotlin/Scala
      • Scanning EAR or WAR files
    • Javascript
    • .NET
      • Scanning DLLs
    • NodeJS
    • Perl
    • PHP
    • Python
    • R
    • Ruby
    • Rust
    • Swift / Objective-C
    • Generic (third party)
  • Special platfoms
  • Unity Packages
  • Jupyter Notebooks
    • License detection
  • Yocto license manifests
  • Container scanner
    • Container Scanner
      • Introduction
      • General usage
      • Command line parameters
        • General configuration
        • Overriding scores
        • Producing reports
        • Defining projects
        • Advanced Options
        • System information
      • How to set a vulnerability exclusion
  • IaC SCANNER
    • Introduction
    • General usage
    • Command line parameters
      • Producing reports
      • Defining projects
    • Policy management page
    • How to set a vulnerability exclusion
  • CI INTEGRATIONS
    • Introduction
    • AWS CodeBuild
    • Azure DevOps
      • Using the Docker image
      • Using the Java Thin client
    • Bamboo
    • Bitrise
    • CircleCI
    • CodeShip
    • Concourse CI
    • Generic CI
    • GitLab CI/CD
      • Docker-in-Docker configuration
      • Meterian Docker image configuration
      • Non-Meterian Docker image configuration
    • Jenkins
      • Pipeline
    • TeamCity
    • TravisCI
  • DevOps Integrations
    • GitLab Ultimate
    • SonarQube
      • Compatibility
      • Download and installation
      • Plugin properties
      • Usage
      • Report page
  • Management Platforms
    • Threadfix
    • DefectDojo
      • Uploading from a CI
    • Armorcode
    • Jira
  • Dedicated Instance
    • Introduction
    • On Cloud (MC/CC)
    • On Premises (OP)
      • Requirements and install
      • Managing the system
        • Admin dashboard
        • Managing your license
        • Managing accounts
    • Using the scanners
      • Thin client
      • Dockerized client
      • Container Scanner
      • IaC Scanner
  • Meterian API
  • API basics
  • Authorizing the APIs
  • Account APIs
    • Knowing your account
    • Listing your projects
  • Samples
  • Guides
    • Managing teams and members
    • Generating reports via APIs
Powered by GitBook
On this page

Was this helpful?

Unity Packages

PreviousGeneric (third party)NextJupyter Notebooks

Last updated 1 month ago

Was this helpful?

Meterian can process packages, either builtins or unity , and open packages from , as long as they are declared using a manifest.json file and a packages-lock.json file, as per standards. If the agent does not find a lock file, it will use only the manifest file but the results will be partial, as transitive dependencies won't be correctly resolved.

The only requirement, assuming your license has the feature enabled, is to add to the client invocation the parameter --scan-unity when running it. Please note that the nodejs scanner is automatically disabled on unit project, unless it's explicitly required, using --scan-nodejs .

An example of run against theproject from Greener-Games:

$ meterian --scan-unity 

Meterian Client v1.2.17.4, build 0000
© 2017-2021 Meterian Ltd - All rights reserved

System information:
- running locally:   yes
- interactive mode:  on
- working on folder: /home/bbossola/projects/rocksolid/samples/tmp.unity/TaskRunner
- autofix mode:      off

Checking folder...
Folder /home/bbossola/projects/rocksolid/samples/tmp.unity/TaskRunner contains a viable project!

Requesting build...
Build allowed

Account: "Meterian Team Account"
- Minimum scores:  
  - security:  95
  - stability: 95
  - licensing: 95
- Analysis scopes:  
  - security:  packaged components
  - stability: all components
  - licensing: all components

Project information:
- url:    https://github.com/Greener-Games/TaskRunner
- branch: master
- commit: e846cf789653bdef95df848bf9f53e12cc0b0d13

Unity scan - running MeterianUnityParser 1.0 locally...
- unity: parsing lockfile...
- unity: dependencies generated...
- unity: collected local license declarations...
Execution successful!

Uploading dependencies information - 50 found...
Done!

Starting build...
Current build status: initialized
Current build status: in preparation
Current build status: process advices at 2021-08-24T14:05:14.269
Current build status: assessment created at 2021-08-24T14:05:26.765

Final results: 
- security:	  100	(minimum: 95)
- stability:	  100	(minimum: 95)
- licensing:	  100	(minimum: 95)

Full report available at: 
https://www.meterian.com/projects/?pid=114d80fb-4e18-aaaa-84d4-0c8ccca96e10&branch=master&mode=eli

Build successful!

Scanning Unity Plugins

It is also possible to process unity plugins:

meterian --scan-unity --process-unity-plugins

Please note that when using this option you will need to use the .

Unity
standard packages
OpenUpm
TaskRunner
Dockerized Client