← Home

@goatlab/node-backend

npm Homepage

Common tools to work with Node.js backend applications.

31
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

cabrerabywatersrobertziberttomcastro

Keywords

typescriptTS

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/compression AI (phantom-deps): @types/* packages are commonly listed as runtime deps in TypeScript libraries for type distribution; not a real phantom dep risk for this package. ai
phantom-deps phantom-dep:@types/response-time AI (phantom-deps): @types/* packages are commonly listed as runtime deps in TypeScript libraries for type distribution; not a real phantom dep risk for this package. ai
phantom-deps phantom-dep:@types/connect-timeout AI (phantom-deps): @types/* packages are commonly listed as runtime deps in TypeScript libraries for type distribution; not a real phantom dep risk for this package. ai
phantom-deps phantom-dep:@types/express-session AI (phantom-deps): @types/* packages are commonly listed as runtime deps in TypeScript libraries for type distribution; not a real phantom dep risk for this package. ai
phantom-deps phantom-dep:@types/express-rate-limit AI (phantom-deps): @types/* packages are commonly listed as runtime deps in TypeScript libraries for type distribution; not a real phantom dep risk for this package. ai

Versions (showing 31 of 31)

Version Deps Published
1.6.3 36 / 27
1.6.2 36 / 27
1.6.1 36 / 27
1.6.0 36 / 27
1.5.6 36 / 27
1.5.5 36 / 27
1.5.4 36 / 27
1.5.3 36 / 27
1.5.2 36 / 27
1.5.1 36 / 27
1.5.0 34 / 27
1.4.1 35 / 27
1.1.21 34 / 27
1.1.20 34 / 27
1.1.19 34 / 27
1.1.17 34 / 27
1.1.14 34 / 27
1.1.13 34 / 27
1.1.11 34 / 27
1.1.10 34 / 27
1.1.8 34 / 27
1.1.7 34 / 27
1.1.6 34 / 27
1.1.5 34 / 27
1.1.4 34 / 27
1.1.3 34 / 27
1.1.2 34 / 27
1.1.1 34 / 27
1.1.0 34 / 29
1.0.1 34 / 29
1.0.0 34 / 29

v1.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.