← Home

@atlassian/atlas-connect

npm Repository Homepage

CLI for the atlassian-connect-express library (helpers for building Atlassian Connect apps on top of Express)

3
Versions
Apache-2.0
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

Keywords

atlassianatlassian connectjirajira service deskconfluencebitbucket

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): CLI tool using execSync for ngrok setup; expected pattern for this developer tooling package. ai
semgrep semgrep:dynamic-require AI (semgrep): Resolves a hardcoded relative path to a local lib module; no user-controlled input involved. ai
phantom-deps phantom-dep:read AI (phantom-deps): read is declared in dependencies; phantom-dep heuristic is a false positive here. ai

Versions (showing 3 of 3)

Version Deps Published
0.11.0 11 / 0
0.10.0 11 / 0
0.9.1 11 / 0

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

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

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