← Home

@longzai-intelligence/shared-kernel-value-object

npm
8
Versions
—
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

joydragon

Keywords

shared-kernelvalue-object

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@longzai-intelligence/zod-utils AI (phantom-deps): Same-org package; likely re-exported or used transitively within the monorepo — stable false positive for this package. ai
npm-metadata no-description AI (npm-metadata): Internal org package; missing description is consistent across the namespace, not a malware indicator. ai
provenance no-provenance AI (provenance): No provenance is common; no other risk signals elevate this for this package. ai

Versions (showing 8 of 8)

Version Deps Published
0.1.4 4 / 23
0.1.3 2 / 11
0.1.2 2 / 11
0.1.1 2 / 11
0.1.0 2 / 11
0.0.3 2 / 11
0.0.2 2 / 11
0.0.1 2 / 11

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

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. Consider requesting the maintainer enable provenance via CI/CD.

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

1 finding
LOW No provenance attestation provenance

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

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