@replayio/app-building
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher has established track record (3 approved pkgs); diff shows no behavioral change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with legitimate maintainer handoff, no malicious diff. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 1.50.0 | 0 / 1 | |
| 1.49.0 | 0 / 1 | |
| 1.48.0 | 0 / 1 | |
| 1.47.0 | 0 / 1 | |
| 1.46.0 | 0 / 1 | |
| 1.45.0 | 0 / 1 | |
| 1.44.0 | 0 / 1 | |
| 1.43.0 | 0 / 1 | |
| 1.42.0 | 0 / 1 | |
| 1.40.2 | 0 / 1 | |
| 1.40.1 | 0 / 1 | |
| 1.40.0 | 0 / 1 | |
| 1.39.0 | 0 / 1 | |
| 1.38.0 | 0 / 1 | |
| 1.37.0 | 0 / 1 | |
| 1.36.0 | 0 / 1 | |
| 1.35.0 | 0 / 1 | |
| 1.34.0 | 0 / 1 | |
| 1.33.0 | 0 / 1 | |
| 1.32.0 | 0 / 1 | |
| 1.31.0 | 0 / 1 | |
| 1.30.0 | 0 / 1 | |
| 1.29.0 | 0 / 1 | |
| 1.28.0 | 0 / 1 | |
| 1.27.0 | 0 / 1 | |
| 1.26.0 | 0 / 1 | |
| 1.25.0 | 0 / 0 | |
| 1.24.1 | 0 / 0 | |
| 1.24.0 | 0 / 0 | |
| 1.23.0 | 0 / 0 | |
| 1.22.0 | 0 / 0 | |
| 1.21.0 | 0 / 0 | |
| 1.20.0 | 0 / 0 | |
| 1.19.1 | 0 / 0 | |
| 1.19.0 | 0 / 0 | |
| 1.18.0 | 0 / 0 | |
| 1.17.0 | 0 / 0 | |
| 1.16.0 | 0 / 0 | |
| 1.15.0 | 0 / 0 | |
| 1.14.0 | 0 / 0 | |
| 1.13.0 | 0 / 0 | |
| 1.12.0 | 0 / 0 | |
| 1.11.0 | 0 / 0 | |
| 1.10.0 | 0 / 0 | |
| 1.9.0 | 0 / 0 | |
| 1.8.3 | 0 / 0 | |
| 1.8.2 | 0 / 0 | |
| 1.8.1 | 0 / 0 | |
| 1.8.0 | 0 / 0 | |
| 1.7.0 | 0 / 0 | |
| 1.6.0 | 0 / 0 |
v1.50.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bhackett1024) than the most recent previously approved version (mwardreplay) on 2026-07-23, but bhackett1024 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mwardreplay) than the most recent previously approved version (bhackett1024) on 2026-07-10, but mwardreplay is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.