npmpackage.info

Gathering detailed insights and metrics for @pinpt/gcp-process-logger

@pinpt/gcp-process-logger - 0.0.7 | npmpackage.info

@pinpt/gcp-process-logger

GCP process logger which will stream the output of a process to GCP Cloud Logging

0.0.7

JavaScript

3.07 kB

3.2

Installations

npm install @pinpt/gcp-process-logger

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

14.17.6

NPM Version

6.14.15 Score

49.6

Supply Chain

Quality

77.1

Maintenance

Vulnerability

98.2

License

Pull Requests

Open

0

Total

5

Closed

0

Merged

5

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Languages

JavaScript

Dockerfile

JavaScript (90.27%)

Dockerfile (9.73%)

Developer

pinpt

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

1 Stars

20 Commits

4 Watchers

2 Branches

5 Contributors

Updated on Sep 07, 2021

Maintainers

View All 5 Contributors

Package Meta Information

Latest Version

0.0.7

Package Id

@pinpt/gcp-process-logger@0.0.7

Unpacked Size

3.07 kB

Size

1.57 kB

File Count

NPM Version

6.14.15

Node Version

14.17.6

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@google-cloud/logging arg

GCP Process Logger

This is a simple wrapper to log the output of a process to GCP Cloud Logging.

Example usage:

1gcp-process-logger my-test-log --label foo=bar --label bar=foo -- npm run build

This will run anything after the -- as the command and pipe the output to the log name passed as the first argument.

Optionally, you can pass one or more labels as --label key=value which will be attached to the metadata of the log entry.

To control a non-default GCP project id, use --project-id=[ID] to setup the logger to use that id.

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

9

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

2

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Security-Policy

Determines if the project has published a security policy.

0

License

Determines if the project has defined a license.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

3.2

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More