@teambit/scripts SEE LICENSE IN UNLICENSED 35 versions

@teambit/scripts

npm Homepage

35

Versions

SEE LICENSE IN UNLICENSED

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

teambit-ownershohamgiladdavidfirstranm8guysaaritaymendelerezbitjoshk2redigmayona007

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	no-description	AI (npm-metadata): Scoped internal package; missing description is stable pattern for this publisher.	ai	2026/05/17
provenance	no-provenance	AI (provenance): Monorepo package; provenance not yet enabled but not a blocker for established publisher.	ai	2026/05/17
dependencies	unvetted-dep:@teambit/harmony	AI (dependencies): Internal teambit ecosystem dependency; consistent with the package's established dependency pattern.	ai	2026/04/30
dependencies	unvetted-dep:@teambit/bit-error	AI (dependencies): Internal teambit ecosystem dependency; consistent with the package's established dependency pattern.	ai	2026/04/30
phantom-deps	phantom-dep:core-js	AI (phantom-deps): Standard Babel polyfill; implicit runtime dep pattern stable across teambit packages.	ai	2026/04/30
phantom-deps	phantom-dep:@babel/runtime	AI (phantom-deps): Framework-scoped Babel runtime; loaded by convention in teambit build output.	ai	2026/04/30

Versions (showing 35 of 235)

Version	Deps	Published
0.0.35	11 / 6	2025-11-20
0.0.34	11 / 6	2025-11-19
0.0.33	11 / 6	2025-11-19
0.0.32	11 / 6	2025-11-19
0.0.31	11 / 6	2025-11-19
0.0.30	11 / 6	2025-11-17
0.0.29	11 / 6	2025-11-17
0.0.28	11 / 6	2025-11-14
0.0.27	11 / 6	2025-11-14
0.0.26	11 / 6	2025-11-14
0.0.25	11 / 6	2025-11-13
0.0.24	11 / 6	2025-11-10
0.0.23	11 / 6	2025-11-10
0.0.22	11 / 6	2025-11-07
0.0.21	11 / 6	2025-11-06
0.0.20	11 / 6	2025-11-05
0.0.19	11 / 6	2025-11-05
0.0.18	11 / 6	2025-11-04
0.0.17	11 / 6	2025-11-03
0.0.16	11 / 6	2025-10-30
0.0.15	11 / 6	2025-10-29
0.0.14	11 / 6	2025-10-28
0.0.13	11 / 6	2025-10-28
0.0.12	11 / 6	2025-10-24
0.0.11	11 / 6	2025-10-23
0.0.10	11 / 6	2025-10-22
0.0.9	11 / 6	2025-10-22
0.0.8	11 / 6	2025-10-21
0.0.7	11 / 6	2025-10-21
0.0.6	11 / 6	2025-10-16
0.0.5	11 / 6	2025-10-16
0.0.4	11 / 6	2025-10-15
0.0.3	11 / 6	2025-10-15
0.0.2	11 / 6	2025-10-14
0.0.1	11 / 6	2025-10-14

v0.0.35

1 finding

LOW No provenance attestation provenance

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

v0.0.34

1 finding

LOW No provenance attestation provenance

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

v0.0.33

1 finding

LOW No provenance attestation provenance

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

v0.0.32

1 finding

LOW No provenance attestation provenance

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

v0.0.31

1 finding

LOW No provenance attestation provenance

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

v0.0.30

1 finding

LOW No provenance attestation provenance

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

v0.0.29

1 finding

LOW No provenance attestation provenance

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

v0.0.28

1 finding

LOW No provenance attestation provenance

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

v0.0.27

1 finding

LOW No provenance attestation provenance

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

v0.0.26

1 finding

LOW No provenance attestation provenance

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

v0.0.25

1 finding

LOW No provenance attestation provenance

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

v0.0.24

1 finding

LOW No provenance attestation provenance

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

v0.0.23

1 finding

LOW No provenance attestation provenance

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

v0.0.22

1 finding

LOW No provenance attestation provenance

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

v0.0.21

1 finding

LOW No provenance attestation provenance

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

v0.0.20

1 finding

LOW No provenance attestation provenance

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

v0.0.19

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

1 finding

LOW No provenance attestation provenance

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

v0.0.17

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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