@starasia/box
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): UI component library with clean history; missing gitHead is a publish-env change, not a security signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Small UI component library; lack of Sigstore provenance is a process gap, not a security indicator for this package. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped UI component package; not a plausible typosquat of got. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped UI component package; not a plausible typosquat of koa. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped UI component package; not a plausible typosquat of zod. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI component package; not a plausible typosquat of joi. | ai | |
| typosquat | typosquat.levenshtein:mobx | AI (typosquat): Scoped UI component package; not a plausible typosquat of mobx. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 0 / 10 | |
| 4.0.0 | 0 / 10 | |
| 3.0.2 | 0 / 10 | |
| 3.0.1 | 0 / 10 | |
| 3.0.0 | 0 / 10 | |
| 2.2.1 | 0 / 10 | |
| 2.2.0 | 0 / 10 | |
| 2.0.2 | 0 / 10 | |
| 2.0.1 | 0 / 10 | |
| 2.0.0 | 0 / 10 | |
| 1.0.5 | 0 / 10 | |
| 1.0.4 | 0 / 10 | |
| 1.0.3 | 0 / 10 | |
| 1.0.2 | 0 / 10 | |
| 1.0.1 | 0 / 10 | |
| 1.0.0 | 0 / 10 |
v4.0.1
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: rizkyizh.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
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: rizkyizh.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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: rizkyizh.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
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: rizkyizh.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.