@codecademy/gamut — Greenflagged

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

codecademy-eng

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/PatternBackdrop/PatternBackdrop.d.ts	AI (source-diff): Long lines are verbose TypeScript generic type declarations, not obfuscation. Stable pattern for this component library.	ai	2026/05/22
phantom-deps	phantom-dep:react-aria-tabpanel	AI (phantom-deps): Declared but not directly imported; consistent pattern for this package's dep management.	ai	2026/05/20
phantom-deps	phantom-dep:polished	AI (phantom-deps): Declared but not directly imported; stable false positive for this package.	ai	2026/05/20
source-diff	obfuscated-file:dist/DatePicker/DatePickerInput/elements.d.ts	AI (source-diff): Long lines are TypeScript declaration file with expanded union types — standard tsc output, not obfuscation.	ai	2026/05/16
source-diff	obfuscated-file:dist/DatePicker/DatePickerCalendar/Calendar/utils/elements.js	AI (source-diff): Long lines are Emotion CSS-in-JS with inline base64 source maps — standard build output, not obfuscation.	ai	2026/05/16
phantom-deps	phantom-dep:@codecademy/gamut-illustrations	AI (phantom-deps): Same-org package; declared as dep for consumers, not directly imported in this package's own code.	ai	2026/04/29
phantom-deps	phantom-dep:@react-aria/interactions	AI (phantom-deps): Referenced in config/overrides; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@types/marked	AI (phantom-deps): Type-only package; not directly imported at runtime by convention.	ai	2026/04/29

Versions (showing 43 of 43)

Version	Deps	Published
71.0.0	24 / 0	2026-06-04
70.0.0	24 / 0	2026-06-01
69.0.0	24 / 0	2026-06-01
68.7.1	24 / 0	2026-05-28
68.7.0	24 / 0	2026-05-27
68.6.2	24 / 0	2026-05-26
68.6.1	24 / 0	2026-05-20
68.6.0	24 / 0	2026-05-14
68.5.1	24 / 0	2026-05-08
68.5.0	24 / 0	2026-05-04
68.4.1	24 / 0	2026-05-04
68.3.0	23 / 0	2026-04-29
68.1.4	23 / 0	2026-03-19
68.1.3	23 / 0	2026-03-18
68.1.2	23 / 0	2026-03-17
68.1.1	23 / 0	2026-03-17
68.1.0	23 / 0	2026-03-12
68.0.5	23 / 0	2026-03-04
68.0.4	24 / 0	2026-03-02
68.0.3	23 / 0	2026-02-19
68.0.2	23 / 0	2026-02-12
68.0.1	23 / 0	2026-02-04
68.0.0	23 / 0	2026-01-29
67.6.5	23 / 0	2026-01-28
67.6.4	23 / 0	2026-01-26
67.6.3	23 / 0	2026-01-12
67.6.2	23 / 0	2026-01-05
67.6.1	23 / 0	2025-12-23
67.6.0	23 / 0	2025-12-10
67.5.4	23 / 0	2025-12-08
67.5.3	23 / 0	2025-12-05
67.5.2	23 / 0	2025-12-04
67.5.1	23 / 0	2025-12-03
67.5.0	23 / 0	2025-12-03
67.4.2	23 / 0	2025-12-03
67.4.1	23 / 0	2025-12-02
67.4.0	23 / 0	2025-12-01
67.3.3	23 / 0	2025-11-13
67.3.2	23 / 0	2025-11-10
67.3.1	23 / 0	2025-11-07
67.3.0	23 / 0	2025-11-04
67.2.1	23 / 0	2025-11-03
67.2.0	23 / 0	2025-11-03

v71.0.0

1 finding

LOW No provenance attestation provenance

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

v70.0.0

1 finding

LOW No provenance attestation provenance

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

v69.0.0

1 finding

LOW No provenance attestation provenance

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

v68.7.1

1 finding

LOW No provenance attestation provenance

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

v68.7.0

1 finding

LOW No provenance attestation provenance

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

v68.6.2

1 finding

LOW No provenance attestation provenance

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

v68.6.1

2 findings

HIGH New obfuscated file: dist/PatternBackdrop/PatternBackdrop.d.ts 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.

v68.6.0

3 findings

HIGH New obfuscated file: dist/DatePicker/DatePickerCalendar/Calendar/utils/elements.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.

HIGH New obfuscated file: dist/DatePicker/DatePickerInput/elements.d.ts 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.

v68.5.1

3 findings

HIGH New obfuscated file: dist/DatePicker/DatePickerCalendar/Calendar/utils/elements.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.

HIGH New obfuscated file: dist/DatePicker/DatePickerInput/elements.d.ts 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.

v68.5.0

3 findings

HIGH New obfuscated file: dist/DatePicker/DatePickerCalendar/Calendar/utils/elements.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.

HIGH New obfuscated file: dist/DatePicker/DatePickerInput/elements.d.ts 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.

v68.4.1

3 findings

HIGH New obfuscated file: dist/DatePicker/DatePickerCalendar/Calendar/utils/elements.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.

HIGH New obfuscated file: dist/DatePicker/DatePickerInput/elements.d.ts 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.

v68.1.4

1 finding

LOW No provenance attestation provenance

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

v68.1.3

1 finding

LOW No provenance attestation provenance

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

v68.1.2

1 finding

LOW No provenance attestation provenance

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

v68.1.1

1 finding

LOW No provenance attestation provenance

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

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

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

v68.0.4

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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

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

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

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

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

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

v67.5.4

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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

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

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

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

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

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

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

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

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