← Home

@llui/devmode-annotate

npm Repository Homepage
12
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

fponticelli

Keywords

lluidevtoolsannotationllmscreenshot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:lexical AI (phantom-deps): Referenced in config files; peer/transitive usage pattern for lexical editor packages is normal. ai
phantom-deps phantom-dep:@lexical/link AI (phantom-deps): Config-file reference; standard lexical plugin pattern. ai
phantom-deps phantom-dep:@lexical/list AI (phantom-deps): Config-file reference; standard lexical plugin pattern. ai
phantom-deps phantom-dep:@llui/lexical AI (phantom-deps): Same-org package; phantom-dep heuristic unreliable for monorepo siblings. ai
phantom-deps phantom-dep:@lexical/table AI (phantom-deps): Config-file reference; standard lexical plugin pattern. ai
phantom-deps phantom-dep:@lexical/utils AI (phantom-deps): Config-file reference; standard lexical plugin pattern. ai
phantom-deps phantom-dep:@lexical/markdown AI (phantom-deps): Config-file reference; standard lexical plugin pattern. ai
phantom-deps phantom-dep:@lexical/code-core AI (phantom-deps): Config-file reference; standard lexical plugin pattern. ai
phantom-deps phantom-dep:@lexical/rich-text AI (phantom-deps): Config-file reference; standard lexical plugin pattern. ai
phantom-deps phantom-dep:@lexical/selection AI (phantom-deps): Config-file reference; standard lexical plugin pattern. ai

Versions (showing 12 of 12)

Version Deps Published
0.2.7 15 / 6
0.2.6 15 / 6
0.2.5 15 / 6
0.2.4 15 / 6
0.2.3 13 / 5
0.2.2 13 / 5
0.2.1 13 / 5
0.2.0 13 / 5
0.1.0 13 / 5
0.0.4 1 / 3
0.0.3 1 / 3
0.0.2 2 / 3

v0.2.7

1 finding
LOW No provenance attestation provenance

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

v0.2.6

1 finding
LOW No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

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.

v0.0.2

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.