← Home

@lytjs/lytjs

npm Repository Homepage

Lyt.js - 轻写轻跑，所见即代码。零依赖超轻量前端框架聚合包

9
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

idcu

Keywords

lytlytjsjavascriptframeworkfrontendvue-likelightweightzero-dependencyreactivevdom

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Aggregator package with no material changes from prior version; missing gitHead reflects a publish environment change but no malicious indicators present. ai
phantom-deps phantom-dep:@lytjs/vdom AI (phantom-deps): Aggregation/umbrella package; @lytjs/vdom is a sibling workspace package bundled into dist output rather than directly imported in source. Same org scope, no external risk. ai

Versions (showing 9 of 9)

Version Deps Published
5.0.1 9 / 0
4.2.0 9 / 0
4.1.0 9 / 0
4.0.5 9 / 0
4.0.4 9 / 0
4.0.1 8 / 0
4.0.0 8 / 0
3.2.1 8 / 0
3.1.0 8 / 0

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.5

1 finding
LOW No provenance attestation provenance

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

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

v4.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.

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.2.1

1 finding
LOW No provenance attestation provenance

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

v3.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.