← Home

@flint.fyi/nuxt

npm Repository Homepage

[Experimental] A Flint plugin for Nuxt code.

5
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

lishaduckmfaithjoshuakgoldberg

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SLSA provenance attestation present; gitHead absence is minor given Sigstore-backed CI publish. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Legitimate experimental package from a highly trusted publisher; 0.0.0 reflects early-stage monorepo release. ai
typosquat typosquat.levenshtein:next AI (typosquat): Scoped package @flint.fyi/nuxt is a Nuxt plugin for the Flint project, not a typosquat of 'next'. ai
bogus-package bogus-package AI (bogus-package): Experimental early-stage plugin; sparse README and empty entry point are expected for this package. ai
phantom-deps phantom-dep:typescript AI (phantom-deps): typescript is a runtime dependency in package.json; phantom-dep is a false positive here. ai

Versions (showing 5 of 5)

Version Deps Published
0.1.6 2 / 1
0.1.5 2 / 1
0.1.4 2 / 1
0.1.3 2 / 1
0.0.0 2 / 1

v0.1.6

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.5

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@flint.fyi/nuxt' is 1 edit(s) away from popular package 'next'.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.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.