@voiceflow/style
Low-level styling and styled component utilities.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.16.0 | 5 / 5 | |
| 1.15.1 | 5 / 5 | |
| 1.15.0 | 5 / 5 | |
| 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 | |
| 1.9.1 | 5 / 5 | |
| 1.9.0 | 5 / 6 | |
| 1.8.0 | 5 / 6 | |
| 1.7.0 | 5 / 10 | |
| 1.6.1 | 5 / 10 | |
| 1.6.0 | 5 / 10 | |
| 1.5.3 | 5 / 10 | |
| 1.5.2 | 5 / 10 | |
| 1.5.1 | 5 / 10 | |
| 1.5.0 | 5 / 10 | |
| 1.4.1 | 5 / 10 | |
| 1.4.0 | 5 / 10 | |
| 1.3.0 | 5 / 10 | |
| 1.2.5 | 5 / 10 | |
| 1.2.4 | 5 / 10 | |
| 1.2.3 | 5 / 10 | |
| 1.2.2 | 5 / 10 | |
| 1.2.1 | 5 / 10 | |
| 1.1.1 | 4 / 10 | |
| 1.1.0 | 4 / 10 |
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.