@microsoft/rayfin-mcp
Rayfin Model Context Protocol tooling
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 |
|---|---|---|---|---|
| source-diff | source-size-dropped | AI (source-diff): Size drop explained by code extraction into sibling @microsoft/rayfin-docs package in same monorepo. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.33.1 | 4 / 7 | |
| 1.33.0 | 4 / 7 | |
| 1.30.0 | 4 / 7 | |
| 1.29.0 | 6 / 8 | |
| 1.28.0 | 6 / 8 | |
| 1.27.0 | 6 / 8 | |
| 1.26.0 | 6 / 8 | |
| 1.24.0 | 6 / 8 | |
| 1.23.0 | 6 / 8 | |
| 1.22.0 | 6 / 8 | |
| 1.21.0 | 6 / 8 | |
| 1.20.0 | 6 / 8 |
v1.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.