@callstack/repack-dev-server
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 | no-provenance | AI (provenance): Established Callstack org package; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| dependencies | unvetted-dep:launch-editor | AI (dependencies): launch-editor is a standard dev-tooling dep used by many React Native toolchains; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:fastify-favicon | AI (dependencies): fastify-favicon is a standard Fastify plugin; expected dependency for this dev server package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.2.5 | 12 / 6 | |
| 5.2.4 | 12 / 5 | |
| 5.2.3 | 12 / 5 | |
| 5.2.2 | 12 / 5 | |
| 5.2.1 | 12 / 5 | |
| 5.2.0 | 12 / 5 | |
| 5.1.3 | 13 / 4 | |
| 5.1.2 | 13 / 4 | |
| 5.1.1 | 13 / 4 |
v5.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.