@codecademy/gamut-tests
Shared component test setup for Gamut applications
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): codecademy-eng matched on email as prior known maintainer; org account rename, not a hijack. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New publisher is the same org, matched on email to prior maintainer. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old account removed as part of org account migration; not a hostile takeover. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Codecademy monorepo CI publishes many packages in rapid succession; pattern is expected and stable. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 6.0.5 | 3 / 0 | |
| 6.0.4 | 3 / 0 | |
| 6.0.3 | 3 / 0 | |
| 6.0.2 | 3 / 0 | |
| 6.0.1 | 3 / 0 | |
| 6.0.0 | 3 / 0 | |
| 5.3.4 | 3 / 0 | |
| 5.3.3 | 3 / 0 | |
| 5.3.2 | 3 / 0 | |
| 5.3.1 | 3 / 0 | |
| 5.3.0 | 3 / 0 | |
| 5.2.22 | 3 / 0 | |
| 5.2.21 | 3 / 0 | |
| 5.2.20 | 3 / 0 | |
| 5.2.19 | 3 / 0 | |
| 5.2.18 | 3 / 0 | |
| 5.2.17 | 3 / 0 | |
| 5.2.16 | 3 / 0 | |
| 5.2.15 | 3 / 0 | |
| 5.2.14 | 3 / 0 | |
| 5.2.13 | 3 / 0 | |
| 5.2.12 | 3 / 0 | |
| 5.2.11 | 3 / 0 | |
| 5.2.10 | 3 / 0 | |
| 5.2.9 | 3 / 0 | |
| 5.2.8 | 3 / 0 | |
| 5.2.7 | 3 / 0 | |
| 5.2.6 | 3 / 0 | |
| 5.2.5 | 3 / 0 | |
| 5.2.4 | 3 / 0 | |
| 5.2.3 | 3 / 0 | |
| 5.2.2 | 3 / 0 | |
| 5.2.1 | 3 / 0 | |
| 5.2.0 | 3 / 0 | |
| 5.1.4 | 3 / 0 | |
| 5.1.3 | 3 / 0 | |
| 5.1.2 | 3 / 0 | |
| 5.1.1 | 3 / 0 | |
| 5.1.0 | 3 / 0 | |
| 5.0.10 | 3 / 0 |
v5.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.