← Home

@andrewcaires/api

npm Repository Homepage

Simple api for small applications using express, jsonwebtoken, sequelize and websocket

17
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

andrewcaires

Keywords

apiauthexpressjsonwebtokenpermissionsroutessequelizetokenvalidationswebsocketweb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:sequelize AI (dependencies): sequelize is a widely-used, well-known ORM; stable false positive for this package. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package under author's own namespace; not a typosquat of pg. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package under author's own namespace; not a typosquat of joi. ai
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped package @andrewcaires/api; not impersonating hapi. Author's own namespace with 77 published versions. ai
phantom-deps phantom-dep:tsx AI (phantom-deps): tsx is used in dev scripts (tsx-dev --watch); stable false positive for this package. ai
phantom-deps phantom-dep:cors AI (phantom-deps): cors is a runtime dep used via express middleware; phantom-dep heuristic misfires here. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped package under author's own namespace; not a typosquat of ajv. ai

Versions (showing 17 of 17)

Version Deps Published
5.2.3 13 / 15
5.2.2 13 / 15
5.2.1 13 / 15
5.2.0 13 / 15
5.1.2 13 / 15
5.1.1 13 / 15
5.1.0 13 / 15
5.0.6 12 / 16
5.0.5 12 / 16
5.0.4 12 / 16
5.0.3 12 / 16
5.0.2 12 / 16
5.0.1 12 / 15
5.0.0 12 / 15
4.5.2 10 / 14
4.5.1 10 / 14
4.5.0 10 / 14

v5.2.3

1 finding
LOW No provenance attestation provenance

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

v5.2.2

1 finding
LOW No provenance attestation provenance

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

v5.2.1

1 finding
LOW No provenance attestation provenance

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

v5.2.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@andrewcaires/api' is 1 edit(s) away from popular package 'hapi'.

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.

v5.1.2

1 finding
LOW No provenance attestation provenance

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

v5.1.1

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@andrewcaires/api' is 1 edit(s) away from popular package 'hapi'.

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.

v5.1.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'hapi' typosquat

Package name '@andrewcaires/api' is 1 edit(s) away from popular package 'hapi'.

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.

v5.0.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.

v5.0.5

1 finding
LOW No provenance attestation provenance

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

v5.0.4

1 finding
LOW No provenance attestation provenance

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

v5.0.3

1 finding
LOW No provenance attestation provenance

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

v5.0.2

1 finding
LOW No provenance attestation provenance

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

v5.0.1

1 finding
LOW No provenance attestation provenance

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

v5.0.0

1 finding
LOW No provenance attestation provenance

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

v4.5.2

1 finding
LOW No provenance attestation provenance

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

v4.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.

v4.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.