@atlaskit/media-filmstrip
Supply chain provenance
Status for the latest visible version.
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
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 @atlaskit/* packages without Sigstore provenance attestation consistently; this is a stable characteristic of this package family. | ai | |
| phantom-deps | phantom-dep:@atlaskit/link | AI (phantom-deps): Same-org @atlaskit/* phantom dep in a monorepo context; declared for transitive/type usage, not a security concern. | ai | |
| phantom-deps | phantom-dep:@atlaskit/theme | AI (phantom-deps): Same-org @atlaskit/* phantom dep in a monorepo context; declared for transitive/type usage, not a security concern. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 51.3.4 | 13 / 12 | |
| 51.3.3 | 13 / 12 | |
| 51.3.2 | 13 / 12 | |
| 51.3.1 | 13 / 12 | |
| 51.3.0 | 13 / 11 | |
| 51.2.11 | 13 / 11 | |
| 51.2.10 | 13 / 11 | |
| 51.2.9 | 13 / 11 | |
| 51.2.8 | 13 / 11 | |
| 51.2.7 | 13 / 11 | |
| 51.2.6 | 13 / 11 | |
| 51.2.5 | 13 / 11 | |
| 51.2.4 | 13 / 11 | |
| 51.2.3 | 13 / 11 | |
| 51.2.2 | 13 / 11 | |
| 51.2.1 | 13 / 11 | |
| 51.2.0 | 13 / 11 | |
| 51.1.10 | 13 / 11 | |
| 51.1.9 | 13 / 11 | |
| 51.1.8 | 13 / 11 | |
| 51.1.7 | 13 / 11 | |
| 51.1.6 | 13 / 11 | |
| 51.1.5 | 13 / 11 | |
| 51.1.4 | 13 / 11 | |
| 51.1.3 | 13 / 11 | |
| 51.1.2 | 13 / 11 | |
| 51.1.1 | 13 / 11 | |
| 51.1.0 | 13 / 11 | |
| 51.0.13 | 13 / 11 | |
| 51.0.12 | 13 / 11 | |
| 51.0.11 | 13 / 11 | |
| 51.0.10 | 13 / 11 | |
| 51.0.9 | 13 / 11 | |
| 51.0.8 | 13 / 11 | |
| 51.0.7 | 13 / 11 | |
| 51.0.6 | 13 / 12 | |
| 51.0.5 | 13 / 12 | |
| 51.0.4 | 13 / 12 | |
| 51.0.3 | 13 / 12 | |
| 51.0.2 | 13 / 12 | |
| 51.0.1 | 13 / 12 | |
| 51.0.0 | 13 / 12 |
v51.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.