@cool-ai/beach-format
Channel Formatter and Content Renderer primitives for batched-edge delivery in Beach applications.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a sibling package in the same Beach monorepo; consistent with normal feature expansion. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.1.14 | 3 / 2 | |
| 1.1.11 | 2 / 2 | |
| 1.1.10 | 2 / 2 | |
| 1.1.9 | 2 / 2 | |
| 1.1.8 | 2 / 2 | |
| 1.1.7 | 2 / 2 | |
| 1.1.6 | 2 / 2 | |
| 1.1.5 | 2 / 2 | |
| 1.1.4 | 2 / 2 | |
| 1.1.3 | 2 / 2 | |
| 1.1.2 | 2 / 2 | |
| 1.1.1 | 2 / 3 | |
| 1.1.0 | 2 / 3 | |
| 1.0.1 | 1 / 3 | |
| 1.0.0 | 1 / 3 | |
| 0.1.0 | 1 / 3 | |
| 0.0.5 | 1 / 3 | |
| 0.0.4 | 1 / 3 | |
| 0.0.3 | 1 / 3 | |
| 0.0.2 | 1 / 3 |
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.