← Home

@atlaskit/forge-react-types

npm Repository Homepage
57
Versions
—
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

atlassianartifactteam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/types/components/__generated__/tokens.codegen.d.ts AI (source-diff): Same codegen pattern as above; stable false positive for this package. ai
source-diff obfuscated-file:dist/types-ts4.5/components/__generated__/tokens.codegen.d.ts AI (source-diff): Codegen-produced TypeScript declaration file; long lines are large token-map object types, not obfuscation. ai
source-diff obfuscated-file:dist/types-ts4.5/components/__generated__/BreadcrumbsItemProps.codegen.d.ts AI (source-diff): Codegen-produced .d.ts with long icon union types; not obfuscated, stable pattern for this package. ai
source-diff obfuscated-file:dist/types/components/__generated__/BreadcrumbsItemProps.codegen.d.ts AI (source-diff): Codegen-produced .d.ts with long icon union types; not obfuscated, stable pattern for this package. ai
source-diff obfuscated-file:dist/types-ts4.5/components/__generated__/BannerProps.codegen.d.ts AI (source-diff): Codegen-produced .d.ts with long icon union types; not obfuscated, stable pattern for this package. ai
source-diff obfuscated-file:dist/types/components/__generated__/BannerProps.codegen.d.ts AI (source-diff): Codegen-produced .d.ts with long icon union types; not obfuscated, stable pattern for this package. ai
dependencies unvetted-dep:@atlaskit/comment AI (dependencies): First-party @atlaskit component from same Atlassian publisher; stable false positive. ai
dependencies unvetted-dep:@atlaskit/tag-group AI (dependencies): First-party @atlaskit component from same Atlassian publisher; stable false positive. ai
dependencies unvetted-dep:@atlaskit/breadcrumbs AI (dependencies): First-party @atlaskit component from same Atlassian publisher; stable false positive. ai
dependencies unvetted-dep:@atlaskit/progress-tracker AI (dependencies): First-party @atlaskit component from same Atlassian publisher; stable false positive. ai
dependencies unvetted-dep:@atlaskit/navigation-system AI (dependencies): First-party @atlaskit component from same Atlassian publisher; stable false positive. ai
dependencies unvetted-dep:@atlaskit/banner AI (dependencies): First-party @atlaskit component from same Atlassian publisher; stable false positive. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used only in dev codegen/typecheck scripts, not in runtime or install hooks. ai

Versions (showing 57 of 57)

Version Deps Published
1.7.0 34 / 9
1.6.2 34 / 9
1.6.1 34 / 9
1.6.0 34 / 9
1.5.0 34 / 9
1.4.0 34 / 9
1.3.2 34 / 9
1.3.1 34 / 9
1.3.0 34 / 9
1.2.0 34 / 9
1.1.0 34 / 9
1.0.9 29 / 9
1.0.8 29 / 9
1.0.7 29 / 9
1.0.6 29 / 9
1.0.5 29 / 8
1.0.4 29 / 7
1.0.3 29 / 7
1.0.2 29 / 7
1.0.1 29 / 7
1.0.0 29 / 7
0.67.0 29 / 7
0.66.0 29 / 7
0.65.3 29 / 7
0.65.2 29 / 7
0.65.1 29 / 7
0.65.0 29 / 7
0.64.0 29 / 7
0.63.2 29 / 7
0.63.1 29 / 7
0.63.0 29 / 7
0.62.0 29 / 7
0.61.0 29 / 7
0.60.0 29 / 7
0.59.0 29 / 7
0.58.0 28 / 7
0.57.1 28 / 7
0.57.0 28 / 7
0.56.2 28 / 7
0.56.1 28 / 7
0.56.0 28 / 7
0.55.0 28 / 7
0.54.0 26 / 7
0.53.0 26 / 7
0.52.2 25 / 7
0.52.1 25 / 7
0.52.0 25 / 7
0.51.1 25 / 7
0.51.0 25 / 7
0.50.0 25 / 7
0.49.2 25 / 7
0.49.1 25 / 7
0.49.0 25 / 7
0.48.0 25 / 7
0.47.2 25 / 7
0.47.1 25 / 7
0.47.0 25 / 7

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.6.2

1 finding
LOW No provenance attestation provenance

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

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.2

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

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

v1.1.0

5 findings
HIGH New obfuscated file: dist/types-ts4.5/components/__generated__/BannerProps.codegen.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.

HIGH New obfuscated file: dist/types/components/__generated__/BannerProps.codegen.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.

HIGH New obfuscated file: dist/types-ts4.5/components/__generated__/BreadcrumbsItemProps.codegen.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.

HIGH New obfuscated file: dist/types/components/__generated__/BreadcrumbsItemProps.codegen.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.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.67.0

1 finding
LOW No provenance attestation provenance

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

v0.66.0

1 finding
LOW No provenance attestation provenance

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

v0.65.3

1 finding
LOW No provenance attestation provenance

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

v0.65.2

1 finding
LOW No provenance attestation provenance

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

v0.65.1

1 finding
LOW No provenance attestation provenance

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

v0.65.0

1 finding
LOW No provenance attestation provenance

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

v0.64.0

1 finding
LOW No provenance attestation provenance

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

v0.63.2

1 finding
LOW No provenance attestation provenance

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

v0.63.1

1 finding
LOW No provenance attestation provenance

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

v0.63.0

1 finding
LOW No provenance attestation provenance

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

v0.62.0

1 finding
LOW No provenance attestation provenance

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

v0.61.0

1 finding
LOW No provenance attestation provenance

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

v0.60.0

1 finding
LOW No provenance attestation provenance

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

v0.59.0

1 finding
LOW No provenance attestation provenance

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

v0.58.0

1 finding
LOW No provenance attestation provenance

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

v0.57.1

1 finding
LOW No provenance attestation provenance

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

v0.57.0

1 finding
LOW No provenance attestation provenance

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

v0.56.2

1 finding
LOW No provenance attestation provenance

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

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

v0.56.0

3 findings
HIGH New obfuscated file: dist/types-ts4.5/components/__generated__/tokens.codegen.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.

HIGH New obfuscated file: dist/types/components/__generated__/tokens.codegen.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.

v0.55.0

3 findings
HIGH New obfuscated file: dist/types-ts4.5/components/__generated__/tokens.codegen.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.

HIGH New obfuscated file: dist/types/components/__generated__/tokens.codegen.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.

v0.54.0

1 finding
LOW No provenance attestation provenance

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

v0.53.0

1 finding
LOW No provenance attestation provenance

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

v0.52.2

1 finding
LOW No provenance attestation provenance

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

v0.52.1

1 finding
LOW No provenance attestation provenance

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

v0.52.0

1 finding
LOW No provenance attestation provenance

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

v0.51.1

1 finding
LOW No provenance attestation provenance

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

v0.51.0

1 finding
LOW No provenance attestation provenance

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

v0.50.0

1 finding
LOW No provenance attestation provenance

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

v0.49.2

1 finding
LOW No provenance attestation provenance

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

v0.49.1

1 finding
LOW No provenance attestation provenance

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

v0.49.0

1 finding
LOW No provenance attestation provenance

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

v0.48.0

1 finding
LOW No provenance attestation provenance

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

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

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