@forge/feature-flags
Feature Flags Node SDK for Atlassian Forge apps running on Node Runtime
12
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
atlassianartifactteam
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Atlassian publishes to their own registry; lack of Sigstore provenance is consistent across their package ecosystem. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.txt | AI (license): Standard Atlassian proprietary license pattern used across their Forge SDK packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 1 / 2 | |
| 2.0.1 | 1 / 2 | |
| 2.0.0 | 1 / 2 | |
| 1.0.8 | 1 / 1 | |
| 1.0.7 | 1 / 1 | |
| 1.0.6 | 1 / 1 | |
| 1.0.5 | 1 / 1 | |
| 1.0.4 | 1 / 1 | |
| 1.0.3 | 1 / 1 | |
| 1.0.2 | 1 / 1 | |
| 1.0.1 | 1 / 1 | |
| 1.0.0 | 1 / 1 |
v2.0.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.