← Home

@viewfly/devtools

npm Repository Homepage

Viewfly is a simple and easy-to-use JavaScript framework with an intuitive development experience.

7
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

viewfly

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require in rollup-plugin-postcss CSS module loader — standard build-tool pattern, not a security risk for this package. ai
phantom-deps phantom-dep:chalk AI (phantom-deps): Phantom dep heuristic false positive; chalk is a common transitive/dev dep in build tooling. ai
phantom-deps phantom-dep:style-inject AI (phantom-deps): style-inject is a known rollup-plugin-postcss bundled dependency pattern, not a real phantom dep risk. ai

Versions (showing 7 of 7)

Version Deps Published
3.0.6 17 / 7
3.0.5 17 / 7
3.0.1 15 / 7
2.2.1 10 / 5
2.2.0 10 / 5
2.1.0 10 / 5
2.0.0 20 / 5

v3.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.