npmpackage.info

Gathering detailed insights and metrics for connect-gitsha

connect-gitsha

Add the application's current git sha as a response header

1.0.0

JavaScript

278.00 B

1,293 2.6

Installations

npm install connect-gitsha

Developer Guide

BETA

Typescript

No

Module System

N/A

Min. Node Version

>= 0.6

NPM Version

1.2.18 Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Contributors

Unable to fetch Contributors

View all 1 contributors

Languages

JavaScript

JavaScript (100%)

Love this project? Help keep it running — sponsor us today! 🚀

Developer

elliotf

Download Statistics

Total Downloads

1,293

Last Day

Last Week

Last Month

Last Year

111

GitHub Statistics

2 Stars

7 Commits

2 Watching

1 Branches

1 Contributors

Bundle Size

396.00 B

Minified

278.00 B

Minified + Gzipped

Bundlephobia

Maintainers

Package Meta Information

Latest Version

1.0.0

Package Id

connect-gitsha@1.0.0

Size

1.82 kB

NPM Version

1.2.18

Total Downloads

Cumulative downloads

Total Downloads

1,293

Last day

Compared to previous day

Last week

Compared to previous week

Last month

-50%

Compared to previous month

Last year

16.8%

111

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

chai mocha nodemon sinon-chai mocha-sinon

Versions

connect-gitsha

Add an 'X-Git-SHA' header to each response

installation

$ npm install connect-gitsha

usage

Like any other middleware:

var express = require('express')
  , gitsha  = require('gitsha')
;

var app = express();

app.use(gitsha());

Why?

Because it's nice to know what rev of your software is running

requirements

git needs to be in the path of the application user
the working directory needs to be within the git repository

No vulnerabilities found.

10

Binary-Artifacts

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

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Code-Review

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

0

SAST

Determines if the project uses static code analysis.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

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

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

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.

Score

2.6

/10

Last Scanned on 2025-02-03

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