@forwardimpact/summit
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@forwardimpact/libutil | AI (dependencies): Internal org dependency from the same forwardimpact namespace; consistent with the package's ecosystem. | ai | |
| dependencies | unvetted-dep:@forwardimpact/libtelemetry | AI (dependencies): Internal org dependency from the same forwardimpact namespace; consistent with the package's ecosystem. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.1.26 | 8 / 1 | |
| 0.1.25 | 8 / 1 | |
| 0.1.24 | 8 / 1 | |
| 0.1.23 | 8 / 1 | |
| 0.1.22 | 7 / 1 | |
| 0.1.21 | 7 / 1 | |
| 0.1.20 | 6 / 1 | |
| 0.1.18 | 6 / 1 | |
| 0.1.16 | 6 / 1 | |
| 0.1.15 | 6 / 1 | |
| 0.1.14 | 6 / 1 | |
| 0.1.13 | 6 / 1 | |
| 0.1.12 | 6 / 1 | |
| 0.1.11 | 6 / 1 | |
| 0.1.10 | 6 / 1 | |
| 0.1.9 | 6 / 1 | |
| 0.1.8 | 6 / 1 | |
| 0.1.7 | 6 / 1 | |
| 0.1.6 | 6 / 0 | |
| 0.1.5 | 6 / 0 | |
| 0.1.4 | 6 / 0 | |
| 0.1.3 | 6 / 0 | |
| 0.1.2 | 6 / 0 | |
| 0.1.1 | 6 / 0 | |
| 0.1.0 | 7 / 0 |
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.