← Home

@flint.fyi/jsx

[Experimental] A Flint plugin for JSX code.

3
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): Package has SLSA provenance attestation which provides stronger integrity guarantee than gitHead; acceptable for this package. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Established trusted publisher; 0.0.0 reflects early experimental monorepo package, not throwaway malware. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Scoped @flint.fyi package; not a typosquat of jest. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped @flint.fyi package; not a typosquat of qs. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @flint.fyi package; not a typosquat of joi. ai
bogus-package bogus-package AI (bogus-package): Experimental plugin in a monorepo; sparse README and empty entry point are expected for early-stage packages. ai

Versions (showing 3 of 3)

Version Deps Published
0.3.2 5 / 4
0.3.1 5 / 4
0.0.0 5 / 4

v0.3.2

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

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.