@microsoft/create-rayfin
Scaffold a Rayfin project with `npm init @microsoft/create-rayfin`.
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): @vscode/deviceid is a legitimate Microsoft/VSCode telemetry package; consistent with this Microsoft scaffolding tool's context. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): CLI spinner library; runtime dependency for bin script, not a phantom. | ai | |
| phantom-deps | phantom-dep:figlet | AI (phantom-deps): ASCII art library; runtime dependency for CLI output, not a phantom. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): Interactive CLI prompts; runtime dependency for scaffolding, not a phantom. | ai | |
| dependencies | unvetted-dep:@azure/monitor-opentelemetry-exporter | AI (dependencies): Beta Azure SDK telemetry exporter; expected dependency for Microsoft tooling, stable pattern for this publisher. | ai | |
| provenance | no-provenance | AI (provenance): Established Microsoft publisher; absence of provenance is common and not a risk signal here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.5.4 | 10 / 7 | |
| 1.5.3 | 10 / 7 | |
| 1.5.0 | 10 / 7 | |
| 1.3.0 | 9 / 7 | |
| 1.2.3 | 9 / 9 | |
| 1.2.2 | 9 / 9 | |
| 1.2.1 | 9 / 9 | |
| 1.2.0 | 6 / 9 | |
| 1.1.0 | 6 / 9 |
v1.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.