@useparagon/whiskers-cattery-git - npm Package Compare versions

Comparing version 0.0.1-canary.18 to 0.0.1-canary.19

dist/steps/git-checkout.step.d.ts

 import { ActionsStepConfig, GithubActionWorkflowStep } from '@useparagon/whiskers-core';
-/**
- * parameters for the checkout step
- */
 export type CheckoutParams = Partial<{
-    ref: string;
+    /**
+     * Whether to execute `git clean -ffdx && git reset --hard HEAD` before fetching
+     *
+     * @default true
+     */
     clean: boolean;
+    /**
+     * Number of commits to fetch. 0 indicates all history for all branches and tags.
+     *
+     * @default 1
+     */
     'fetch-depth': number;
     /**
-     * Personal access token (PAT) used to fetch the repository. The PAT is configured
-     * with the local git config, which enables your scripts to run authenticated git
-     * commands. The post-job step removes the PAT.
+     * Whether to fetch tags, even if fetch-depth > 0.
      *
-     * We recommend using a service account with the least permissions necessary. Also
-     * when generating a new PAT, select the least scopes necessary.
+     * @default false
+     */
+    'fetch-tags': boolean;
+    /**
+     * Partially clone against a given filter. Overrides sparse-checkout if set.
      *
+     * @default null
+     */
+    filter: string;
+    /**
+     * The base URL for the GitHub instance that you are trying to clone from, will use environment defaults to fetch from the same instance that the workflow is running from unless specified. Example URLs are https://github.com or https://my-ghes-server.example.com
+     */
+    'github-server-url': string;
+    /**
+     * Whether to download Git-LFS files
+     *
+     * @default false
+     */
+    lfs: boolean;
+    /**
+     * Relative path under $GITHUB_WORKSPACE to place the repository
+     */
+    path: string;
+    /**
+     * Whether to configure the token or SSH key with the local git config
+     *
+     * @default true
+     */
+    'persist-credentials': boolean;
+    /**
+     * The branch, tag or SHA to checkout. When checking out the repository that triggered a workflow, this defaults to the reference or SHA for that event.  Otherwise, uses the default branch.
+     */
+    ref: string;
+    /**
+     * Repository name with owner. For example, actions/checkout
+     *
+     * @default ${{ github.repository }}
+     */
+    repository: string;
+    /**
+     * Add repository path as safe.directory for Git global config by running `git config --global --add safe.directory <path>`
+     *
+     * @default true
+     */
+    'set-safe-directory': boolean;
+    /**
+     * Whether to show progress status output when fetching.
+     *
+     * @default true
+     */
+    'show-progress': boolean;
+    /**
+     * Do a sparse checkout on given patterns. Each pattern should be separated with new lines.
+     *
+     * @default null
+     */
+    'sparse-checkout': string;
+    /**
+     * Specifies whether to use cone-mode when doing a sparse checkout.
+     *
+     * @default true
+     */
+    'sparse-checkout-cone-mode': boolean;
+    /**
+     * SSH key used to fetch the repository. The SSH key is configured with the local git config, which enables your scripts to run authenticated git commands. The post-job step removes the SSH key.
+     *
+     * We recommend using a service account with the least permissions necessary.
+     *
      * [Learn more about creating and using encrypted secrets](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)
+     */
+    'ssh-key': string;
+    /**
+     * Known hosts in addition to the user and global host key database. The public SSH keys for a host may be obtained using the utility `ssh-keyscan`. For example, `ssh-keyscan github.com`. The public key for github.com is always implicitly added.
+     */
+    'ssh-known-hosts': string;
+    /**
+     * Whether to perform strict host key checking. When true, adds the options `StrictHostKeyChecking=yes` and `CheckHostIP=no` to the SSH command line. Use the input `ssh-known-hosts` to configure additional hosts.
      *
-     * Default: ${{ github.token }}
+     * @default true
      */
+    'ssh-strict': boolean;
+    /**
+     * The user to use when connecting to the remote SSH host. By default 'git' is used.
+     *
+     * @default git
+     */
+    'ssh-user': string;
+    /**
+     * Whether to checkout submodules: `true` to checkout submodules or `recursive` to recursively checkout submodules.
+     *
+     * When the `ssh-key` input is not provided, SSH URLs beginning with `[e-mail]:` are converted to HTTPS.
+     *
+     * @default false
+     */
+    submodules: boolean;
+    /**
+     * Personal access token (PAT) used to fetch the repository. The PAT is configured with the local git config, which enables your scripts to run authenticated git commands. The post-job step removes the PAT.
+     *
+     * We recommend using a service account with the least permissions necessary. Also when generating a new PAT, select the least scopes necessary.
+     *
+     * [Learn more about creating and using encrypted secrets](https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)
+     *
+     * @default ${{ github.token }}
+     */
     token: string;
@@ -22,0 +123,0 @@ }>;

dist/steps/git-checkout.step.js

@@ -7,3 +7,3 @@ "use strict";
     name: 'checkout',
-    uses: 'actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c', // v3.3.0
+    uses: 'actions/checkout@a5ac7e51b41094c92402da3b24376905380afc29', // v4.1.6
     with: {
@@ -10,0 +10,0 @@ clean: true,

package.json

 {
   "name": "@useparagon/whiskers-cattery-git",
-  "version": "0.0.1-canary.18",
+  "version": "0.0.1-canary.19",
   "bugs": "https://github.com/useparagon/whiskers/issues",
@@ -19,3 +19,3 @@ "homepage": "https://github.com/useparagon/whiskers#readme",
     "tslib": "^2.6.2",
-    "@useparagon/whiskers-core": "0.0.1-canary.18"
+    "@useparagon/whiskers-core": "0.0.1-canary.19"
   },
@@ -22,0 +22,0 @@ "scripts": {

Fixed alerts

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

12710

increased by41.74%

Lines of code

300

increased by50.75%

Number of medium supply chain risk alerts

0

decreased by-100%

Dependency changes

• + Added@useparagon/whiskers-core@0.0.1-canary.19(transitive)

• - Removed@useparagon/whiskers-core@0.0.1-canary.18(transitive)

• Updated@useparagon/whiskers-core@0.0.1-canary.19