← Home

@axinom/mosaic-message-bus

npm

Messaging library for Axinom Mosaic services

12
Versions
PROPRIETARY
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

schwendneraxinom_kuzminruwanxaxinomnpm

Keywords

axinommosaicaxinom mosaic

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:src/signing/register-public-signing-key.spec.ts AI (source-diff): Long encoded strings are RSA key fixtures in test files for signing functionality — not obfuscated payloads. ai
source-diff encoded-string-file:src/middleware/validate-signed-event-middleware.spec.ts AI (source-diff): RSA key test fixtures for validate-signed-event middleware tests; benign for this crypto-signing package. ai
semgrep semgrep:base64-decode AI (semgrep): Standard JWT payload decoding pattern; not a malicious payload. ai
bogus-package bogus-package AI (bogus-package): Proprietary commercial package from Axinom; sparse README and no public repo are expected for internal/commercial libs. ai

Versions (showing 12 of 12)

Version Deps Published
0.49.0 12 / 18
0.48.0 12 / 18
0.47.0 12 / 16
0.46.0 12 / 16
0.45.0 12 / 16
0.44.0 12 / 16
0.43.0 12 / 16
0.42.0 12 / 16
0.41.0 12 / 16
0.40.0 12 / 16
0.39.1 12 / 16
0.39.0 12 / 16

v0.49.0

1 finding
LOW No provenance attestation provenance

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

v0.48.0

3 findings
HIGH Long encoded string in modified file: src/signing/register-public-signing-key.spec.ts source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: src/middleware/validate-signed-event-middleware.spec.ts source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.46.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.45.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.44.0

1 finding
LOW No provenance attestation provenance

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

v0.43.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.42.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.41.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.40.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.39.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.39.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.