← Home

@forge/api

npm

Forge API methods

16
Versions
SEE LICENSE IN LICENSE.txt
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
typosquat typosquat.levenshtein:hapi AI (typosquat): @forge/api is Atlassian's official scoped package; not a typosquat of hapi. ai
typosquat typosquat.levenshtein:pg AI (typosquat): @forge/api is Atlassian's official scoped package; not a typosquat of pg. ai
typosquat typosquat.levenshtein:joi AI (typosquat): @forge/api is Atlassian's official scoped package; not a typosquat of joi. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): @forge/api is Atlassian's official scoped package; not a typosquat of ajv. ai
phantom-deps phantom-dep:headers-utils AI (phantom-deps): headers-utils is a declared runtime dependency; phantom-dep heuristic is a false positive here. ai

Versions (showing 16 of 16)

Version Deps Published
7.2.1 6 / 10
7.2.0 6 / 10
7.1.4 6 / 10
7.1.3 6 / 10
7.1.2 6 / 10
7.1.1 6 / 10
7.1.0 6 / 10
7.0.2 6 / 10
7.0.1 6 / 10
7.0.0 6 / 10
6.4.3 6 / 10
6.4.2 6 / 10
6.4.1 7 / 10
6.4.0 7 / 10
6.3.0 7 / 10
6.2.0 7 / 10

v7.2.1

1 finding
LOW No provenance attestation provenance

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

v7.2.0

1 finding
LOW No provenance attestation provenance

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

v7.1.1

1 finding
LOW No provenance attestation provenance

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

v7.1.0

1 finding
LOW No provenance attestation provenance

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

v7.0.2

1 finding
LOW No provenance attestation provenance

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

v7.0.1

1 finding
LOW No provenance attestation provenance

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

v7.0.0

1 finding
LOW No provenance attestation provenance

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

v6.4.3

1 finding
LOW No provenance attestation provenance

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

v6.4.2

1 finding
LOW No provenance attestation provenance

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

v6.4.1

1 finding
LOW No provenance attestation provenance

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

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

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

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