← Home

@voiceflow/style

Low-level styling and styled component utilities.

8
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

pmvrmcamandasteinhauerandrewlawrencetylerhhaneffervescentiajosh_vfvoiceflow-gallaganz4o4zsssoflyyyxavidopzhilightytolunsanasarjanjughazyandandonovan78theprofabuyakninabondarpixelzarrohan-mandhotra-vfose-voiceflowbreamjbydeleyvf-serviceaccountchidi-voiceflowpateriackdevinabaghmar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Voiceflow org rotates team members regularly; service account publisher provides continuity. ai
maintainer-change maintainer-removed AI (maintainer-change): Same org rotation pattern; no evidence of hostile takeover. ai
source-diff large-new-source-files AI (source-diff): Build refactor (CJS/ESM → unified build) plausibly explains 84 new files; no suspicious content flagged. ai

Versions (showing 8 of 8)

Version Deps Published
1.14.0 5 / 2
1.13.0 5 / 2
1.12.2 5 / 2
1.12.1 5 / 2
1.12.0 5 / 3
1.11.0 5 / 3
1.10.0 5 / 5
1.9.2 5 / 5

v1.14.0

1 finding
LOW No provenance attestation provenance

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

v1.13.0

1 finding
LOW No provenance attestation provenance

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

v1.12.2

1 finding
LOW No provenance attestation provenance

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

v1.12.0

1 finding
LOW No provenance attestation provenance

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

v1.11.0

1 finding
LOW No provenance attestation provenance

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

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