@atlaskit/media-file-preview
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Same org-wide rename; provenance direction unchanged vs prior approved. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same-org Atlassian feature-flag dep, declared config-side; stable FP for this package. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Provenance shows atlaskit-user is a known maintainer, matched by email; not a real takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal accompanies known-maintainer add; not a hijack indicator here. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known Atlassian accounts, part of routine org rotation. | ai | |
| phantom-deps | phantom-dep:@atlassian/react-compiler-gating | AI (phantom-deps): Atlassian-internal config-only dep; declared but not directly imported, consistent with build tooling usage. | ai | |
| source-diff | obfuscated-file:dist/types/globalScope/originalScriptCode.d.ts | AI (source-diff): TypeScript declaration file for the same documented source reference pattern; long lines are URL-encoded JSDoc, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/types-ts4.5/globalScope/originalScriptCode.d.ts | AI (source-diff): TypeScript declaration file for the same documented source reference pattern; long lines are URL-encoded JSDoc, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/globalScope/originalScriptCode.js | AI (source-diff): Same pattern as cjs variant — documented source reference with URL-encoded JSDoc, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/es2019/globalScope/originalScriptCode.js | AI (source-diff): Same pattern as cjs variant — documented source reference with URL-encoded JSDoc, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/globalScope/originalScriptCode.js | AI (source-diff): File is a documented human-readable source reference for a minification workflow; long lines are URL-encoded JSDoc examples, not obfuscated payload. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes all @atlaskit packages without Sigstore provenance; this is consistent across their entire package ecosystem and not a risk indicator. | ai |
Versions (showing 51 of 59)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 9 / 13 | |
| 1.0.2 | 9 / 13 | |
| 1.0.1 | 9 / 13 | |
| 1.0.0 | 8 / 14 | |
| 0.18.0 | 8 / 14 | |
| 0.17.2 | 8 / 12 | |
| 0.17.1 | 8 / 12 | |
| 0.17.0 | 8 / 11 | |
| 0.16.5 | 8 / 11 | |
| 0.16.4 | 8 / 11 | |
| 0.16.3 | 9 / 11 | |
| 0.16.2 | 9 / 11 | |
| 0.16.1 | 9 / 10 | |
| 0.16.0 | 9 / 10 | |
| 0.15.5 | 9 / 11 | |
| 0.15.4 | 9 / 11 | |
| 0.15.3 | 9 / 11 | |
| 0.15.2 | 9 / 11 | |
| 0.15.1 | 9 / 11 | |
| 0.15.0 | 9 / 11 | |
| 0.14.1 | 9 / 11 | |
| 0.14.0 | 9 / 11 | |
| 0.13.0 | 9 / 10 | |
| 0.12.0 | 9 / 10 | |
| 0.11.9 | 9 / 10 | |
| 0.11.8 | 9 / 10 | |
| 0.11.7 | 9 / 10 | |
| 0.11.6 | 9 / 12 | |
| 0.11.5 | 8 / 12 | |
| 0.11.4 | 8 / 12 | |
| 0.11.3 | 8 / 12 | |
| 0.11.2 | 8 / 12 | |
| 0.11.1 | 8 / 12 | |
| 0.9.7 | 8 / 12 | |
| 0.9.5 | 8 / 12 | |
| 0.9.4 | 8 / 12 | |
| 0.9.3 | 8 / 12 | |
| 0.9.2 | 8 / 12 | |
| 0.9.1 | 8 / 12 | |
| 0.9.0 | 8 / 12 | |
| 0.8.4 | 8 / 12 | |
| 0.8.3 | 8 / 12 | |
| 0.8.2 | 8 / 12 | |
| 0.8.1 | 8 / 12 | |
| 0.8.0 | 8 / 12 | |
| 0.7.0 | 7 / 12 | |
| 0.6.0 | 7 / 12 | |
| 0.5.2 | 7 / 13 | |
| 0.5.1 | 7 / 13 | |
| 0.5.0 | 7 / 13 | |
| 0.4.2 | 7 / 13 |
v0.11.1
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-04-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2025-01-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
4 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
This version was published by a different npm account than previous versions on 2024-12-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
3 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atlaskit-user) than the most recent previously approved version (atlaskit) on 2024-11-29, but atlaskit-user is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.9.3
3 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atlaskit-user) than the most recent previously approved version (atlaskit) on 2024-11-28, but atlaskit-user is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.9.2
3 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atlaskit-user) than the most recent previously approved version (atlaskit) on 2024-11-01, but atlaskit-user is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.9.1
3 findingsAll previous maintainers (atlaskit) were replaced by new maintainers (atlassianartifactteam, atlaskit-user). This is a strong signal of a potential package hijack and requires careful review.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atlaskit-user) than the most recent previously approved version (atlaskit) on 2024-10-28, but atlaskit-user is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.