← Home

@vlalg-nimbus/nb-images

npm Repository Homepage

Images components for Vuejs 3

13
Versions
—
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

tonhaosantos

Keywords

vuejsvue jsvue pluginimagesimageimage previewimage galleryimage sliderimage carouselimage viewerimage zoomimage cropimage resizeimage rotateimage flipimage blurimage contrastimage brightnessimage saturationimage huecomponentscomponentvue componentsvuejs componentsvue js components

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
email-domain unclaimed-email:vem lavar a louca gamers AI (email-domain): Team name used as email display field, not an actual domain; real homepage and GitHub org confirm legitimate publisher. ai
phantom-deps phantom-dep:@vlalg-nimbus/bee-css-reset AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on CSS/layout packages not directly imported in JS. ai
phantom-deps phantom-dep:@vlalg-nimbus/chameleon-grid-layout AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on CSS/layout packages not directly imported in JS. ai

Versions (showing 13 of 13)

Version Deps Published
2.4.0 3 / 15
2.3.0 3 / 15
2.2.0 3 / 15
2.1.0 3 / 15
2.0.7 3 / 15
2.0.6 3 / 15
2.0.5 3 / 15
2.0.4 3 / 15
2.0.3 3 / 15
2.0.2 3 / 15
2.0.1 3 / 15
2.0.0 3 / 15
1.0.0 3 / 15

v2.4.0

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. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.6

1 finding
LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

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

v2.0.1

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.

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