← Home

msgpack-lite

npm Repository Homepage

Fast Pure JavaScript MessagePack Encoder and Decoder

15
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

kawanet

Keywords

arraybufferbufferfluentdmessagepackmsgpackserializestreamtypedarrayuint8array

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): All additions are optionalDependencies for benchmark scripts, not runtime-critical. ai
dependencies unvetted-dep:msgpack AI (dependencies): Optional benchmark-comparison dep, loaded via try/catch require, not core functionality. ai
dependencies unvetted-dep:msgpack-js-v5 AI (dependencies): Optional benchmark-comparison dep, same pattern as other msgpack impls. ai
dependencies unvetted-dep:msgpack.codec AI (dependencies): Maintainer's own repo via git URL, used only for benchmarking. ai
dependencies unvetted-dep:msgpack-unpack AI (dependencies): Optional benchmark-comparison dep. ai
npm-metadata url-dep:msgpack.codec AI (npm-metadata): Git URL points to maintainer's own repo, used only for optional benchmarking. ai
npm-metadata url-dep:msgpack-javascript AI (npm-metadata): Dev-only dependency pointing to publisher's own repo; no runtime risk. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is in lib/benchmark.js's try_require helper, used to optionally load competing msgpack libs for benchmarking. Not in runtime code path; no security risk. ai

Versions (showing 15 of 15)

Version Deps Published
0.1.26 4 / 8
0.1.20 4 / 8
0.1.19 4 / 8
0.1.18 4 / 8
0.1.17 2 / 8
0.1.16 1 / 8
0.1.15 1 / 8
0.1.14 8 / 7
0.1.13 1 / 12
0.1.11 0 / 10
0.1.9 0 / 10
0.1.7 0 / 10
0.1.5 0 / 10
0.1.2 0 / 10
0.0.1 0 / 10

v0.1.20

1 finding
LOW No provenance attestation provenance

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

v0.1.19

1 finding
LOW No provenance attestation provenance

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

v0.1.18

1 finding
LOW No provenance attestation provenance

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

v0.1.17

1 finding
LOW No provenance attestation provenance

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

v0.1.16

1 finding
LOW No provenance attestation provenance

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

v0.1.15

1 finding
LOW No provenance attestation provenance

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

v0.1.14

1 finding
LOW No provenance attestation provenance

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

v0.1.13

1 finding
LOW No provenance attestation provenance

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

v0.1.11

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

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