get-workspaces MIT 24 versions

get-workspaces

npm Repository Homepage

Get workspaces for yarn workspaces, bolt workspaces, or the root package for building repo-agnostic tools

24

Versions

MIT

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

andaristemmatownnovinychangesets-release-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): changesets-release-bot is the official release automation account for the changesets monorepo; this transition from noviny is a documented, legitimate handoff with 667 approved packages and 0 rejections.	ai	2026/04/24
publish-pattern	dormant-publish	AI (publish-pattern): The changesets monorepo has periodic release cadences; dormancy followed by a bot-published release with no material changes is consistent with normal maintenance for this package.	ai	2026/04/23
phantom-deps	phantom-dep:globby	AI (phantom-deps): globby is a declared runtime dependency; phantom detection likely fails to trace imports through compiled dist output.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): andarist (Artem Zakharchenko) is a well-known contributor closely associated with the changesets project; this addition is a legitimate and expected maintainer change.	ai	2026/04/23
phantom-deps	phantom-dep:read-yaml-file	AI (phantom-deps): read-yaml-file is a declared runtime dependency; phantom detection likely fails to trace imports through compiled dist output.	ai	2026/04/23
phantom-deps	phantom-dep:@changesets/types	AI (phantom-deps): @changesets/types is a declared runtime dependency; phantom detection likely fails to trace imports through compiled dist output.	ai	2026/04/23
phantom-deps	phantom-dep:fs-extra	AI (phantom-deps): fs-extra is a declared runtime dependency; phantom detection likely fails to trace imports through compiled dist output.	ai	2026/04/23

Versions (showing 24 of 24)

Version	Deps	Published
1.0.11	4 / 0	2023-11-28
1.0.10	4 / 0	2022-12-18
1.0.9	4 / 0	2022-10-01
1.0.8	4 / 0	2022-07-22
1.0.7	4 / 0	2022-03-27
1.0.6	4 / 0	2022-02-19
1.0.5	4 / 0	2021-11-26
1.0.4	4 / 0	2021-08-31
1.0.3	4 / 0	2021-04-08
1.0.2	4 / 0	2020-05-11
1.0.1	4 / 1	2020-04-15
1.0.0	4 / 1	2020-03-11
0.6.0	4 / 1	2020-01-24
0.5.2	3 / 1	2019-10-31
0.5.1	3 / 1	2019-10-31
0.5.0	2 / 1	2019-09-13
0.4.2	2 / 1	2019-09-10
0.4.0	2 / 1	2019-07-05
0.3.1	2 / 1	2019-06-07
0.3.0	2 / 1	2019-05-31
0.2.1	2 / 1	2019-05-21
0.2.0	2 / 1	2019-05-21
0.1.1	2 / 1	2019-05-08
0.1.0	2 / 1	2019-05-08

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

1 finding

LOW No provenance attestation provenance

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

v1.0.9

1 finding

LOW No provenance attestation provenance

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

v1.0.8

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

2 findings

HIGH Publisher changed: noviny → changesets-release-bot (on 2020-04-15) provenance

This version was published by a different npm account than previous versions on 2020-04-15. 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.

v1.0.0

2 findings

HIGH Publisher changed: noviny → changesets-release-bot (on 2020-03-11) provenance

This version was published by a different npm account than previous versions on 2020-03-11. 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.6.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mitchellhamilton → noviny (on 2020-01-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-01-24. This could indicate a legitimate maintainer transition or an account compromise.

v0.5.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: noviny → mitchellhamilton (on 2019-10-31) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-10-31. This could indicate a legitimate maintainer transition or an account compromise.

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

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