@forge/os
Forge Object Store SDK
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @forge/os is Atlassian's official scoped SDK, not a typosquat of 'qs'. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): @forge/os is Atlassian's official scoped SDK, not a typosquat of 'koa'. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @forge/os is Atlassian's official scoped SDK, not a typosquat of 'got'. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @forge/os is Atlassian's official scoped SDK, not a typosquat of 'pg'. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @forge/os is Atlassian's official scoped SDK, not a typosquat of 'cors'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @forge/os is Atlassian's official scoped SDK, not a typosquat of 'joi'. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): @forge/os is Atlassian's official scoped SDK, not a typosquat of 'zod'. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.1.20 | 1 / 3 | |
| 2.1.19 | 1 / 3 | |
| 2.1.18 | 1 / 3 | |
| 2.1.17 | 1 / 3 | |
| 2.1.16 | 1 / 3 | |
| 2.1.15 | 1 / 3 | |
| 2.1.14 | 1 / 3 | |
| 2.1.13 | 1 / 3 | |
| 2.1.12 | 1 / 3 | |
| 2.1.11 | 1 / 3 | |
| 2.1.10 | 1 / 3 | |
| 2.1.9 | 1 / 3 | |
| 2.1.8 | 1 / 3 | |
| 2.1.7 | 1 / 3 | |
| 2.1.6 | 1 / 3 | |
| 2.1.5 | 1 / 3 | |
| 2.1.4 | 1 / 3 | |
| 2.1.3 | 1 / 3 | |
| 2.1.2 | 1 / 3 | |
| 2.1.1 | 1 / 3 | |
| 2.1.0 | 1 / 3 | |
| 2.0.5 | 1 / 3 | |
| 2.0.4 | 1 / 3 | |
| 2.0.3 | 1 / 3 | |
| 2.0.2 | 1 / 3 | |
| 2.0.1 | 1 / 3 | |
| 2.0.0 | 1 / 3 |
v2.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.