← Home

tiny-lr

npm Repository Homepage

Tiny LiveReload server, background-friendly

26
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

elwayman02shamamklabs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from mklabs to elwayman02 occurred in 2016 (~9 years ago) and is a long-settled, legitimate maintainer transition. elwayman02 has 24 approved packages and 0 rejections. ai
publish-pattern new-deps-added AI (publish-pattern): object-assign is a well-known, widely-used polyfill with no malicious history. This is a benign dependency addition. ai

Versions (showing 26 of 26)

Version Deps Published
2.0.0 6 / 14
1.1.1 6 / 14
1.1.0 6 / 14
1.0.5 6 / 14
1.0.4 6 / 14
1.0.3 6 / 14
1.0.2 5 / 14
1.0.1 5 / 14
1.0.0 5 / 14
0.2.1 6 / 7
0.2.0 6 / 7
0.1.7 6 / 7
0.1.6 6 / 7
0.1.5 6 / 8
0.1.4 5 / 8
0.1.3 5 / 8
0.1.1 6 / 8
0.1.0 6 / 8
0.0.9 6 / 8
0.0.8 6 / 8
0.0.7 4 / 5
0.0.5 4 / 5
0.0.4 4 / 5
0.0.3 3 / 3
0.0.2 4 / 2
0.0.1 4 / 2

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

2 findings
HIGH Publisher changed: mklabs → elwayman02 (on 2016-11-01) provenance

This version was published by a different npm account than previous versions on 2016-11-01. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: shama → mklabs (on 2016-10-15) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-10-15. This could indicate a legitimate maintainer transition or an account compromise.

v0.0.4

1 finding
LOW No provenance attestation provenance

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