framesync
A frame-synced render loop for JavaScript
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established package with trusted publisher; missing gitHead is a publish-environment artifact, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance adoption; no security risk from its absence. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 6.1.2 | 1 / 0 | |
| 6.1.1 | 1 / 0 | |
| 6.1.0 | 1 / 0 | |
| 6.0.1 | 1 / 0 | |
| 6.0.0 | 1 / 0 | |
| 5.3.0 | 1 / 3 | |
| 5.2.3 | 1 / 3 | |
| 5.2.2 | 1 / 3 | |
| 5.2.1 | 1 / 3 | |
| 5.2.0 | 0 / 3 | |
| 5.1.0 | 0 / 3 | |
| 5.0.0 | 0 / 3 | |
| 4.1.0 | 1 / 3 | |
| 4.0.4 | 2 / 9 | |
| 4.0.3 | 2 / 8 | |
| 4.0.2 | 1 / 8 | |
| 4.0.1 | 1 / 8 | |
| 4.0.0 | 1 / 8 | |
| 3.1.9 | 0 / 5 | |
| 3.1.8 | 0 / 5 | |
| 3.1.7 | 0 / 3 | |
| 3.1.6 | 0 / 3 | |
| 3.1.5 | 0 / 3 | |
| 3.1.4 | 0 / 3 | |
| 3.1.3 | 0 / 3 | |
| 3.1.2 | 0 / 3 | |
| 3.1.1 | 0 / 3 | |
| 3.1.0 | 0 / 3 | |
| 3.0.2 | 0 / 3 | |
| 3.0.1 | 0 / 3 | |
| 3.0.0 | 0 / 3 | |
| 2.0.1 | 0 / 0 | |
| 2.0.0 | 0 / 0 | |
| 1.0.1 | 0 / 9 | |
| 1.0.0 | 0 / 9 | |
| 0.5.0 | 0 / 9 | |
| 0.4.0 | 0 / 9 | |
| 0.3.0 | 0 / 9 | |
| 0.2.0 | 0 / 9 | |
| 0.1.0 | 0 / 9 |
v6.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: popmotion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: popmotion.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.