@axinom/mosaic-id-link-be PROPRIETARY 11 versions

@axinom/mosaic-id-link-be

npm

Integration utilities from id-service for Axinom Mosaic services

11

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.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Axinom org package with 921 versions and 4 approved packages; diff shows only test script changes, consistent with routine maintenance.	ai	2026/05/01
phantom-deps	phantom-dep:graphql	AI (phantom-deps): graphql is a peer/codegen dependency for this GraphQL integration package; phantom-dep is a stable false positive here.	ai	2026/04/30
phantom-deps	phantom-dep:graphql-tag	AI (phantom-deps): graphql-tag used in codegen config; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@axinom/mosaic-core	AI (phantom-deps): Same-org dependency used indirectly; stable false positive for this Axinom package.	ai	2026/04/30

Versions (showing 11 of 11)

Version	Deps	Published
0.38.0	8 / 7	2026-05-21
0.37.0	8 / 7	2026-04-23
0.36.0	8 / 8	2026-02-26
0.35.0	8 / 8	2026-01-14
0.34.0	8 / 8	2025-11-19
0.33.0	8 / 8	2025-10-08
0.32.0	8 / 8	2025-09-09
0.31.7	8 / 8	2025-07-15
0.31.6	8 / 8	2025-06-20
0.31.5	8 / 8	2025-06-04
0.31.4	8 / 8	2025-04-29

v0.38.0

1 finding

LOW No provenance attestation provenance

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

v0.37.0

1 finding

LOW No provenance attestation provenance

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

v0.35.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.34.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.33.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.32.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.31.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.31.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.

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

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