@mesadev/rest Apache-2.0 35 versions

@mesadev/rest

npm Repository Homepage

TypeScript REST SDK for the Mesa API

35

Versions

Apache-2.0

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

markovejnovicmesa-ci-botolivergilannmitchem

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@hey-api/client-fetch	AI (phantom-deps): @hey-api/client-fetch is a legitimate declared runtime dependency in this REST SDK; its use in config files rather than direct imports is consistent with generated SDK patterns.	ai	2026/04/26
typosquat	typosquat.levenshtein:jest	AI (typosquat): @mesadev/rest is a scoped REST SDK package; 'rest' is a common word describing its purpose, not a typosquat of 'jest'. This finding is a stable false positive for this package.	ai	2026/04/25
typosquat	typosquat.levenshtein:next	AI (typosquat): @mesadev/rest is a scoped REST SDK; 2-edit distance from 'next' is coincidental. Not a typosquat.	ai	2026/04/25
typosquat	typosquat.levenshtein:react	AI (typosquat): @mesadev/rest is a scoped REST SDK; 2-edit distance from 'react' is coincidental. Not a typosquat.	ai	2026/04/25

Versions (showing 35 of 35)

Version	Deps	Published
0.33.0	0 / 0	2026-05-27
0.32.0	0 / 0	2026-05-22
0.31.0	0 / 0	2026-05-22
0.30.0	0 / 2	2026-05-20
0.29.3	0 / 2	2026-05-19
0.29.2	0 / 1	2026-05-17
0.29.1	0 / 1	2026-05-16
0.29.0	0 / 1	2026-05-16
0.28.2	0 / 1	2026-05-08
0.28.1	0 / 1	2026-05-06
0.28.0	0 / 1	2026-05-03
0.27.0	0 / 1	2026-04-30
0.26.0	0 / 1	2026-04-29
0.25.0	0 / 1	2026-04-25
0.24.0	0 / 1	2026-04-23
0.23.0	0 / 1	2026-04-17
0.22.0	0 / 1	2026-04-11
0.21.0	0 / 1	2026-04-09
0.20.0	0 / 1	2026-04-08
0.19.0	0 / 1	2026-04-08
0.18.0	0 / 1	2026-04-08
0.17.0	0 / 1	2026-04-07
0.16.0	0 / 1	2026-04-06
0.15.0	0 / 1	2026-04-02
0.13.4	1 / 2	2026-04-01
0.13.1	1 / 2	2026-04-01
0.11.7	1 / 2	2026-03-30
0.11.1	1 / 2	2026-03-28
0.6.2	1 / 2	2026-03-21
0.6.1	1 / 2	2026-03-20
0.6.0	1 / 2	2026-03-20
0.5.0	1 / 2	2026-03-19
0.4.1	1 / 2	2026-03-18
0.4.0	1 / 1	2026-03-18
0.3.3	1 / 1	2026-03-10

v0.33.0

1 finding

LOW No provenance attestation provenance

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

v0.32.0

1 finding

LOW No provenance attestation provenance

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

v0.31.0

1 finding

LOW No provenance attestation provenance

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

v0.30.0

1 finding

LOW No provenance attestation provenance

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

v0.29.3

1 finding

LOW No provenance attestation provenance

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

v0.29.2

1 finding

LOW No provenance attestation provenance

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

v0.29.1

1 finding

LOW No provenance attestation provenance

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

v0.29.0

1 finding

LOW No provenance attestation provenance

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

v0.28.2

1 finding

LOW No provenance attestation provenance

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

v0.28.1

1 finding

LOW No provenance attestation provenance

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

v0.28.0

1 finding

LOW No provenance attestation provenance

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

v0.27.0

1 finding

LOW No provenance attestation provenance

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

v0.26.0

1 finding

LOW No provenance attestation provenance

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

v0.25.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'jest' typosquat

Package name '@mesadev/rest' is 1 edit(s) away from popular package 'jest'.

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.

v0.24.0

1 finding

LOW No provenance attestation provenance

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

v0.23.0

1 finding

LOW No provenance attestation provenance

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

v0.22.0

1 finding

LOW No provenance attestation provenance

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

v0.21.0

1 finding

LOW No provenance attestation provenance

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

v0.20.0

1 finding

LOW No provenance attestation provenance

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

v0.19.0

1 finding

LOW No provenance attestation provenance

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

v0.18.0

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.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.

v0.15.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.

v0.13.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.

v0.13.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.

v0.11.7

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.

v0.11.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.

v0.6.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.

v0.6.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.

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

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

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

v0.4.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.

v0.3.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.