@atlaskit/analytics-gas-types
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
Keywords
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 monorepo pipeline changes explain dormancy; publisher has 13k+ approved packages and strong track record. | ai | |
| provenance | missing-githead | AI (provenance): Atlassian artifact team pipeline change; consistent with other Atlaskit packages published via same mechanism. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a standard transpilation runtime dependency declared by convention in Atlaskit packages; not a real phantom dep risk. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes via their artifact team pipeline without Sigstore provenance; consistent across all their packages and not a risk signal. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 2 / 0 | |
| 5.1.8 | 2 / 0 | |
| 5.1.7 | 2 / 1 | |
| 5.1.6 | 2 / 1 | |
| 5.1.5 | 2 / 2 | |
| 5.1.4 | 2 / 2 | |
| 5.1.3 | 2 / 2 | |
| 5.1.2 | 2 / 3 | |
| 5.1.1 | 2 / 3 | |
| 5.1.0 | 2 / 3 | |
| 5.0.10 | 2 / 3 | |
| 5.0.9 | 2 / 3 | |
| 5.0.8 | 2 / 3 | |
| 5.0.7 | 2 / 3 | |
| 5.0.6 | 2 / 3 | |
| 5.0.5 | 2 / 2 | |
| 5.0.4 | 2 / 2 | |
| 5.0.3 | 2 / 2 | |
| 5.0.2 | 2 / 1 | |
| 5.0.1 | 2 / 1 | |
| 5.0.0 | 2 / 1 |
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.