@viewfly/cli
A command-line tool for creating Viewfly project templates.
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 | no-provenance | AI (provenance): Established package with clean history; lack of Sigstore attestation is a process gap, not a security indicator. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): CLI tool; ora is a declared runtime dep used in bundled output, heuristic false positive. | ai | |
| phantom-deps | phantom-dep:table | AI (phantom-deps): Declared runtime dep in a bundled CLI; phantom-dep heuristic fires on bundled code. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): Declared runtime dep; bundled CLI pattern causes false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:@types/fs-extra | AI (phantom-deps): Type-only dep; framework-scoped, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/git-clone | AI (phantom-deps): Type-only dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@inquirer/prompts | AI (phantom-deps): Declared runtime dep; bundled CLI pattern causes false phantom-dep detection. | ai | |
| phantom-deps | phantom-dep:git-clone | AI (phantom-deps): Core scaffolding dep; bundled output triggers phantom-dep heuristic. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @viewfly/cli package; Levenshtein match to 'joi' is coincidental, not a squatting attempt. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 6 / 7 | |
| 3.0.0 | 6 / 7 | |
| 2.2.0 | 6 / 7 | |
| 2.1.0 | 13 / 15 | |
| 2.0.0 | 13 / 15 |
v3.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: viewfly.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.