@tmagic/stage
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:scenejs | AI (dependencies): scenejs is a known animation library; expected dep for a visual editor stage component. | ai | |
| dependencies | unvetted-dep:@scena/guides | AI (dependencies): Known UI ruler/guides library from the @scena ecosystem; consistent with stage component. | ai | |
| dependencies | unvetted-dep:moveable-helper | AI (dependencies): moveable-helper is a companion to the moveable drag library; expected for this package. | ai | |
| provenance | no-provenance | AI (provenance): Tencent monorepo package with 248 published versions; no provenance is consistent across all prior releases. | ai | |
| phantom-deps | phantom-dep:scenejs | AI (phantom-deps): scenejs is a declared runtime dep used in config; phantom-dep heuristic fires but it's a legitimate dependency. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.7.13 | 8 / 2 | |
| 1.7.12 | 8 / 2 | |
| 1.7.11 | 8 / 2 | |
| 1.7.10 | 8 / 2 | |
| 1.7.9 | 7 / 2 | |
| 1.7.8 | 7 / 2 | |
| 1.7.7 | 7 / 2 | |
| 1.7.6 | 7 / 2 | |
| 1.7.5 | 7 / 2 | |
| 1.7.4 | 7 / 2 | |
| 1.7.3 | 7 / 2 | |
| 1.7.2 | 7 / 2 | |
| 1.7.1 | 7 / 2 | |
| 1.7.0 | 7 / 2 | |
| 1.6.1 | 7 / 2 | |
| 1.6.0 | 7 / 2 | |
| 1.5.24 | 7 / 2 | |
| 1.5.23 | 7 / 2 | |
| 1.5.22 | 7 / 2 | |
| 1.5.21 | 7 / 2 | |
| 1.5.20 | 7 / 2 | |
| 1.5.19 | 7 / 2 | |
| 1.5.18 | 7 / 2 | |
| 1.5.17 | 7 / 2 |
v1.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.