← Home

lazy-property

npm Repository Homepage

Lazily initialized properties for objects

4
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mikolalysenko

Keywords

lazypropertyobjectinitializearraydictionary

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): This is the legitimate first version of a 12+ year old package with 138k weekly downloads. Version 0.0.0 reflects early npm conventions, not malicious intent. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years; absence is expected and not a risk signal for this package. ai

Versions (showing 4 of 4)

Version Deps Published
1.0.0 0 / 1
0.0.2 0 / 1
0.0.1 0 / 1
0.0.0 0 / 1

v1.0.0

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

v0.0.1

1 finding
INFO No provenance attestation provenance

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

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