broadway
Lightweight App extensibility and hookable middleware customization.
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 | publisher-changed | AI (provenance): Publisher change (jcrugzz → indexzero) occurred in 2016; indexzero is Charlie Robbins, the original author of broadway/flatiron. Legitimate transition, stable for this package. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 3 / 5 | |
| 4.0.0 | 3 / 5 | |
| 3.1.1 | 3 / 6 | |
| 3.1.0 | 3 / 6 | |
| 3.0.0 | 3 / 6 | |
| 2.1.1 | 3 / 6 | |
| 2.1.0 | 3 / 6 | |
| 2.0.1 | 3 / 6 | |
| 2.0.0 | 3 / 6 | |
| 1.2.0 | 3 / 6 | |
| 1.1.1 | 3 / 6 | |
| 1.1.0 | 3 / 6 | |
| 1.0.0 | 3 / 6 | |
| 0.3.6 | 5 / 3 | |
| 0.3.5 | 5 / 3 | |
| 0.3.4 | 5 / 3 | |
| 0.3.3 | 5 / 3 | |
| 0.3.2 | 5 / 3 | |
| 0.3.1 | 5 / 3 | |
| 0.3.0 | 5 / 3 | |
| 0.2.10 | 5 / 3 | |
| 0.2.9 | 5 / 3 | |
| 0.2.8 | 5 / 3 | |
| 0.2.7 | 5 / 3 | |
| 0.2.6 | 5 / 3 | |
| 0.2.5 | 5 / 3 | |
| 0.2.4 | 5 / 3 | |
| 0.2.3 | 5 / 3 | |
| 0.2.1 | 6 / 3 | |
| 0.2.0 | 7 / 3 | |
| 0.1.15 | 7 / 3 | |
| 0.1.14 | 7 / 3 | |
| 0.1.13 | 7 / 3 | |
| 0.1.11 | 7 / 3 | |
| 0.1.10 | 7 / 3 | |
| 0.1.9 | 7 / 3 | |
| 0.1.8 | 5 / 4 | |
| 0.1.7 | 5 / 4 | |
| 0.1.6 | 5 / 4 | |
| 0.1.5 | 5 / 4 | |
| 0.1.4 | 5 / 1 | |
| 0.1.3 | 5 / 1 | |
| 0.1.2 | 5 / 1 | |
| 0.1.1 | 5 / 1 | |
| 0.1.0 | 6 / 1 |
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
2 findingsThis version was published by a different npm account than previous versions on 2016-07-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.