@forge/metrics
Forge internal metrics
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Atlassian org publisher with strong track record; dormancy consistent with internal tooling release cadence. | ai | |
| phantom-deps | phantom-dep:@forge/runtime | AI (phantom-deps): Same-org Atlassian Forge package; declared as runtime dep even if not directly imported in source. | ai |
Versions (showing 51 of 87)
| Version | Deps | Published |
|---|---|---|
| 1.0.2 | 2 / 3 | |
| 1.0.1 | 2 / 3 | |
| 1.0.0 | 2 / 3 | |
| 0.3.29 | 2 / 2 | |
| 0.3.28 | 2 / 2 | |
| 0.3.27 | 2 / 2 | |
| 0.3.26 | 2 / 2 | |
| 0.3.25 | 2 / 2 | |
| 0.3.24 | 2 / 2 | |
| 0.3.23 | 2 / 2 | |
| 0.3.22 | 2 / 2 | |
| 0.3.21 | 2 / 2 | |
| 0.3.20 | 2 / 2 | |
| 0.3.19 | 2 / 2 | |
| 0.3.18 | 2 / 2 | |
| 0.3.17 | 2 / 2 | |
| 0.3.16 | 2 / 2 | |
| 0.3.15 | 2 / 2 | |
| 0.3.14 | 2 / 2 | |
| 0.3.13 | 2 / 2 | |
| 0.3.12 | 2 / 2 | |
| 0.3.11 | 2 / 2 | |
| 0.3.10 | 2 / 2 | |
| 0.3.9 | 2 / 2 | |
| 0.3.8 | 2 / 2 | |
| 0.3.7 | 2 / 2 | |
| 0.3.6 | 2 / 2 | |
| 0.3.5 | 2 / 2 | |
| 0.3.4 | 3 / 0 | |
| 0.3.3 | 3 / 0 | |
| 0.3.2 | 3 / 0 | |
| 0.3.1 | 3 / 0 | |
| 0.2.26 | 3 / 0 | |
| 0.2.25 | 3 / 0 | |
| 0.2.24 | 3 / 0 | |
| 0.2.23 | 3 / 0 | |
| 0.2.22 | 3 / 0 | |
| 0.2.21 | 3 / 0 | |
| 0.2.20 | 3 / 0 | |
| 0.2.19 | 3 / 0 | |
| 0.2.18 | 3 / 0 | |
| 0.2.17 | 3 / 0 | |
| 0.2.16 | 3 / 0 | |
| 0.2.15 | 3 / 0 | |
| 0.2.14 | 3 / 0 | |
| 0.2.13 | 3 / 0 | |
| 0.2.12 | 3 / 0 | |
| 0.2.11 | 3 / 0 | |
| 0.2.10 | 3 / 0 | |
| 0.2.9 | 3 / 0 | |
| 0.2.8 | 3 / 0 |
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atlassianartifactteam) than the most recent previously approved version (atlassian-cicd) on 2025-02-10, but atlassianartifactteam is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.23
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atlassianartifactteam) than the most recent previously approved version (atlassian-cicd) on 2025-01-28, but atlassianartifactteam is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.