@webstudio-is/sdk-components-animation LicenseRef-Webstudio,Inc-Proprietary 39 versions

@webstudio-is/sdk-components-animation

npm Homepage

Webstudio components for animation

39

Versions

LicenseRef-Webstudio,Inc-Proprietary

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

koftrysound

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:lib/index-DhGZj8eD.js	AI (source-diff): Minified by esbuild per documented build script; not obfuscation, stable pattern for this package.	ai	2026/05/11
phantom-deps	phantom-dep:change-case	AI (phantom-deps): Config-referenced dep in a monorepo build; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:shallow-equal	AI (phantom-deps): Config-referenced dep in a monorepo build; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@webstudio-is/icons	AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages.	ai	2026/04/29
phantom-deps	phantom-dep:nanostores	AI (phantom-deps): Config-referenced dep in a monorepo build; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@webstudio-is/css-engine	AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages.	ai	2026/04/29
bogus-package	bogus-package	AI (bogus-package): Legitimate Webstudio org component package; short README and no keywords are expected for internal SDK packages.	ai	2026/04/29
phantom-deps	phantom-dep:react-error-boundary	AI (phantom-deps): Config-referenced dep in a monorepo build; stable false positive for this package.	ai	2026/04/29

Versions (showing 39 of 39)

Version	Deps	Published
0.268.0	8 / 17	2026-06-01
0.267.0	8 / 17	2026-05-09
0.266.0	8 / 17	2026-04-29
0.265.0	8 / 17	2026-04-29
0.264.0	8 / 17	2026-04-27
0.263.0	8 / 17	2026-04-25
0.262.1	8 / 17	2026-04-23
0.262.0	8 / 17	2026-04-19
0.261.1	8 / 17	2026-04-16
0.261.0	8 / 17	2026-04-15
0.260.2	8 / 17	2026-04-12
0.259.0	8 / 17	2026-04-11
0.258.0	8 / 17	2026-03-28
0.257.0	8 / 17	2026-03-24
0.255.0	8 / 17	2026-02-19
0.254.0	8 / 17	2026-02-11
0.253.0	8 / 17	2026-02-05
0.252.2	8 / 17	2026-02-05
0.252.1	8 / 17	2026-01-28
0.238.0	8 / 17	2025-12-08
0.237.0	8 / 17	2025-12-07
0.236.0	8 / 17	2025-12-05
0.235.0	8 / 17	2025-11-23
0.234.0	8 / 17	2025-11-11
0.233.0	8 / 17	2025-11-07
0.232.0	8 / 17	2025-11-04
0.231.0	8 / 17	2025-10-15
0.230.0	8 / 17	2025-10-01
0.229.0	8 / 17	2025-09-07
0.228.0	8 / 17	2025-08-12
0.227.0	8 / 17	2025-08-04
0.226.0	8 / 17	2025-08-03
0.225.0	8 / 17	2025-07-18
0.224.0	8 / 17	2025-07-11
0.223.0	8 / 17	2025-07-02
0.222.0	8 / 17	2025-06-27
0.221.0	8 / 17	2025-06-09
0.220.0	8 / 17	2025-05-19
0.219.0	8 / 17	2025-05-11

v0.268.0

1 finding

LOW No provenance attestation provenance

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

v0.267.0

1 finding

LOW No provenance attestation provenance

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

v0.266.0

1 finding

LOW No provenance attestation provenance

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

v0.264.0

1 finding

LOW No provenance attestation provenance

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

v0.263.0

1 finding

LOW No provenance attestation provenance

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

v0.262.1

1 finding

LOW No provenance attestation provenance

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

v0.262.0

1 finding

LOW No provenance attestation provenance

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

v0.261.1

1 finding

LOW No provenance attestation provenance

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

v0.261.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.

v0.260.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.

v0.259.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.

v0.258.0

1 finding

LOW No provenance attestation provenance

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

v0.257.0

1 finding

LOW No provenance attestation provenance

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

v0.255.0

1 finding

LOW No provenance attestation provenance

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

v0.254.0

1 finding

LOW No provenance attestation provenance

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

v0.253.0

1 finding

LOW No provenance attestation provenance

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

v0.252.2

1 finding

LOW No provenance attestation provenance

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

v0.252.1

1 finding

LOW No provenance attestation provenance

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

v0.238.0

1 finding

LOW No provenance attestation provenance

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

v0.237.0

1 finding

LOW No provenance attestation provenance

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

v0.236.0

2 findings

HIGH Publisher changed: kof → trysound (on 2025-12-05) provenance

This version was published by a different npm account than previous versions on 2025-12-05. 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.

v0.235.0

1 finding

LOW No provenance attestation provenance

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

v0.234.0

1 finding

LOW No provenance attestation provenance

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

v0.233.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.

v0.232.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.

v0.231.0

2 findings

HIGH New obfuscated file: lib/index-DhGZj8eD.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.230.0

2 findings

HIGH New obfuscated file: lib/index-DhGZj8eD.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.229.0

2 findings

HIGH New obfuscated file: lib/index-DhGZj8eD.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.228.0

2 findings

HIGH New obfuscated file: lib/index-DhGZj8eD.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.227.0

2 findings

HIGH New obfuscated file: lib/index-DhGZj8eD.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.226.0

2 findings

HIGH New obfuscated file: lib/index-DhGZj8eD.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.225.0

1 finding

LOW No provenance attestation provenance

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

v0.224.0

1 finding

LOW No provenance attestation provenance

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

v0.223.0

1 finding

LOW No provenance attestation provenance

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

v0.222.0

1 finding

LOW No provenance attestation provenance

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

v0.221.0

1 finding

LOW No provenance attestation provenance

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

v0.220.0

1 finding

LOW No provenance attestation provenance

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

v0.219.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.