@storybook/react-native-web-vite MIT 59 versions

@storybook/react-native-web-vite

npm Repository Homepage

Storybook for React Native Web and Vite: Develop, document, and test UI components in isolation

59

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

dannyhwgongregyannbfshilmanvalentinpalkovicjreinholdtmeasdayndelangenstorybook-bot

Keywords

storybookreact-nativereact-native-webexpoexpo-webvitecomponentcomponents

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:vite-plugin-babel	AI (dependencies): vite-plugin-babel is a legitimate Vite plugin; stable dependency for this Storybook framework package.	ai	2026/05/08
phantom-deps	phantom-dep:@babel/preset-react	AI (phantom-deps): Babel preset loaded by convention via vite-plugin-babel/preset config, not direct import.	ai	2026/05/04
phantom-deps	phantom-dep:@babel/plugin-transform-modules-commonjs	AI (phantom-deps): Babel plugin loaded by convention, not direct import.	ai	2026/05/04
phantom-deps	phantom-dep:@joshwooding/vite-plugin-react-docgen-typescript	AI (phantom-deps): Referenced in config files per analyzer note; not a phantom dep concern.	ai	2026/05/04
provenance	publisher-changed	AI (provenance): jreinhold is a known Storybook core maintainer; manual publish from their account is expected alongside CI-based releases.	ai	2026/05/04
phantom-deps	phantom-dep:@storybook/builder-vite	AI (phantom-deps): @storybook/builder-vite is a direct dependency in package.json; phantom-dep is a false positive for this package.	ai	2026/04/29

Versions (showing 59 of 59)

Version	Deps	Published
10.4.2	5 / 2	2026-06-02
10.4.1	5 / 2	2026-05-22
10.4.0	5 / 2	2026-05-14
10.3.6	5 / 2	2026-04-29
10.3.5	5 / 2	2026-04-07
10.3.4	5 / 2	2026-04-02
10.3.3	5 / 2	2026-03-23
10.3.2	5 / 2	2026-03-23
10.3.1	5 / 2	2026-03-19
10.3.0	5 / 2	2026-03-18
10.2.19	5 / 2	2026-03-13
10.2.18	5 / 2	2026-03-13
10.2.17	5 / 2	2026-03-09
10.2.16	5 / 2	2026-03-06
10.2.15	5 / 2	2026-03-04
10.2.14	5 / 2	2026-03-02
10.2.13	5 / 2	2026-02-26
10.2.12	5 / 2	2026-02-24
10.2.11	5 / 2	2026-02-23
10.2.10	5 / 2	2026-02-18
10.2.9	5 / 2	2026-02-17
10.2.8	5 / 2	2026-02-09
10.2.7	5 / 2	2026-02-05
10.2.6	5 / 2	2026-02-04
10.2.5	5 / 2	2026-02-04
10.2.4	5 / 2	2026-02-02
10.2.3	5 / 2	2026-01-30
10.2.2	5 / 2	2026-01-30
10.2.1	5 / 2	2026-01-27
10.2.0	5 / 2	2026-01-21
10.1.11	5 / 2	2025-12-29
10.1.10	5 / 2	2025-12-17
10.1.9	5 / 2	2025-12-15
10.1.8	5 / 2	2025-12-12
10.1.7	5 / 2	2025-12-11
10.1.6	5 / 2	2025-12-10
10.1.5	5 / 2	2025-12-09
10.1.4	5 / 2	2025-12-03
10.1.3	5 / 2	2025-12-02
10.1.2	5 / 2	2025-11-28
10.1.1	5 / 2	2025-11-28
10.1.0	5 / 2	2025-11-26
10.0.8	5 / 2	2025-11-17
10.0.7	5 / 2	2025-11-11
10.0.6	5 / 2	2025-11-07
10.0.5	5 / 2	2025-11-05
10.0.4	5 / 2	2025-11-04
10.0.3	5 / 2	2025-11-03
10.0.2	5 / 2	2025-10-30
10.0.1	5 / 2	2025-10-29
10.0.0	5 / 2	2025-10-28
9.1.20	5 / 2	2026-03-05
9.1.19	5 / 2	2026-02-18
9.1.18	5 / 2	2026-02-17
9.1.17	5 / 2	2025-12-17
8.6.18	11 / 2	2026-03-06
8.6.17	11 / 2	2026-02-18
8.6.16	11 / 2	2026-02-17
8.6.15	11 / 2	2025-12-17

v10.4.2

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.

v10.4.1

1 finding

LOW No provenance attestation provenance

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

v10.4.0

1 finding

LOW No provenance attestation provenance

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

v10.3.6

1 finding

LOW No provenance attestation provenance

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

v10.3.4

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.

v10.3.3

1 finding

LOW No provenance attestation provenance

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

v10.3.2

1 finding

LOW No provenance attestation provenance

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

v10.3.1

1 finding

LOW No provenance attestation provenance

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

v10.3.0

1 finding

LOW No provenance attestation provenance

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

v10.2.19

1 finding

LOW No provenance attestation provenance

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

v10.2.18

1 finding

LOW No provenance attestation provenance

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

v10.2.17

1 finding

LOW No provenance attestation provenance

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

v10.2.16

1 finding

LOW No provenance attestation provenance

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

v10.2.15

1 finding

LOW No provenance attestation provenance

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

v10.2.14

1 finding

LOW No provenance attestation provenance

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

v10.2.13

1 finding

LOW No provenance attestation provenance

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

v10.2.12

1 finding

LOW No provenance attestation provenance

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

v10.2.11

1 finding

LOW No provenance attestation provenance

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

v10.2.10

1 finding

LOW No provenance attestation provenance

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

v10.2.9

1 finding

LOW No provenance attestation provenance

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

v10.2.8

1 finding

LOW No provenance attestation provenance

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

v10.2.7

1 finding

LOW No provenance attestation provenance

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

v10.2.6

1 finding

LOW No provenance attestation provenance

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

v10.2.5

1 finding

LOW No provenance attestation provenance

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

v10.2.4

1 finding

LOW No provenance attestation provenance

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

v10.2.3

1 finding

LOW No provenance attestation provenance

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

v10.2.2

1 finding

LOW No provenance attestation provenance

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

v10.2.1

1 finding

LOW No provenance attestation provenance

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

v10.2.0

1 finding

LOW No provenance attestation provenance

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

v10.1.11

1 finding

LOW No provenance attestation provenance

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

v10.1.10

1 finding

LOW No provenance attestation provenance

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

v10.1.9

1 finding

LOW No provenance attestation provenance

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

v10.1.8

1 finding

LOW No provenance attestation provenance

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

v10.1.7

1 finding

LOW No provenance attestation provenance

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

v10.1.6

1 finding

LOW No provenance attestation provenance

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

v10.1.5

1 finding

LOW No provenance attestation provenance

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

v10.1.4

1 finding

LOW No provenance attestation provenance

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

v10.1.3

1 finding

LOW No provenance attestation provenance

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

v10.1.2

1 finding

LOW No provenance attestation provenance

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

v10.1.1

1 finding

LOW No provenance attestation provenance

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

v10.1.0

1 finding

LOW No provenance attestation provenance

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

v10.0.8

1 finding

LOW No provenance attestation provenance

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

v10.0.7

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.

v10.0.6

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.

v10.0.5

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.

v10.0.4

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.

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

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

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

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

v9.1.20

1 finding

LOW No provenance attestation provenance

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

v9.1.19

1 finding

LOW No provenance attestation provenance

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

v9.1.18

1 finding

LOW No provenance attestation provenance

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

v9.1.17

2 findings

HIGH Publisher changed: GitHub Actions → jreinhold (on 2025-12-17) provenance

This version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v8.6.18

1 finding

LOW No provenance attestation provenance

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

v8.6.17

1 finding

LOW No provenance attestation provenance

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

v8.6.16

1 finding

LOW No provenance attestation provenance

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

v8.6.15

2 findings

HIGH Publisher changed: GitHub Actions → storybook-bot (on 2025-12-17) provenance

This version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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