@forge/lint
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:eslint | AI (typosquat): Scoped @forge/lint is an official Atlassian Forge tool, not a typosquat of eslint. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped @forge/lint is an official Atlassian Forge tool, not a typosquat of pino. | ai | |
| phantom-deps | phantom-dep:cross-spawn | AI (phantom-deps): cross-spawn is a declared runtime dependency; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 6.0.2 | 10 / 7 | |
| 6.0.1 | 10 / 7 | |
| 6.0.0 | 10 / 7 | |
| 5.19.2 | 9 / 7 | |
| 5.19.1 | 9 / 7 | |
| 5.19.0 | 9 / 7 | |
| 5.18.1 | 9 / 7 | |
| 5.18.0 | 9 / 7 | |
| 5.17.0 | 9 / 7 | |
| 5.16.2 | 9 / 7 | |
| 5.16.1 | 9 / 7 | |
| 5.16.0 | 9 / 7 | |
| 5.15.1 | 9 / 7 | |
| 5.15.0 | 9 / 7 | |
| 5.14.0 | 9 / 7 | |
| 5.13.3 | 9 / 7 | |
| 5.13.2 | 9 / 7 | |
| 5.13.1 | 9 / 7 | |
| 5.13.0 | 9 / 7 | |
| 5.12.1 | 9 / 7 | |
| 5.12.0 | 9 / 7 | |
| 5.11.6 | 9 / 7 | |
| 5.11.5 | 9 / 7 | |
| 5.11.4 | 9 / 7 | |
| 5.11.3 | 9 / 7 | |
| 5.11.2 | 9 / 7 | |
| 5.11.1 | 9 / 7 | |
| 5.11.0 | 9 / 7 | |
| 5.10.2 | 9 / 7 | |
| 5.10.1 | 9 / 7 | |
| 5.10.0 | 9 / 7 | |
| 5.9.1 | 9 / 7 | |
| 5.9.0 | 9 / 7 | |
| 5.8.1 | 9 / 7 | |
| 5.8.0 | 9 / 7 | |
| 5.7.5 | 9 / 7 | |
| 5.7.4 | 9 / 7 | |
| 5.7.0 | 9 / 7 | |
| 5.6.7 | 8 / 7 | |
| 5.6.6 | 8 / 7 | |
| 5.6.5 | 8 / 7 | |
| 5.6.4 | 8 / 7 | |
| 5.6.3 | 8 / 7 | |
| 5.6.2 | 8 / 7 | |
| 5.6.1 | 8 / 7 | |
| 5.6.0 | 8 / 7 | |
| 5.5.1 | 8 / 7 | |
| 5.5.0 | 8 / 7 | |
| 5.4.2 | 8 / 7 | |
| 5.4.1 | 8 / 7 | |
| 5.4.0 | 8 / 7 |
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.4
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.
v5.6.3
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-13, 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.
v5.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.