@atlaskit/eslint-plugin-platform
The essential plugin for use with Atlassian frontend platform tools
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/rules/editor-example-type-import-required/index.js | AI (source-diff): Standard Babel CJS build output with inlined helpers; content is readable ESLint rule logic, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/es2019/rules/editor-example-type-import-required/index.js | AI (source-diff): Standard Babel ES2019 build output; same pattern as CJS variant, no malicious content. | ai | |
| source-diff | obfuscated-file:dist/esm/rules/editor-example-type-import-required/index.js | AI (source-diff): Standard Babel ESM build output; same pattern, no malicious content. | ai | |
| dependencies | unvetted-dep:@atlaskit/eslint-utils | AI (dependencies): Internal Atlassian dependency; consistent with this package's ecosystem and publisher track record. | ai | |
| dependencies | unvetted-dep:@compiled/eslint-plugin | AI (dependencies): Atlassian-maintained compiled CSS-in-JS ESLint plugin; expected dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes many packages without provenance; consistent pattern across their ecosystem. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.10.7 | 12 / 6 | |
| 2.10.6 | 12 / 6 | |
| 2.10.5 | 12 / 6 | |
| 2.10.4 | 12 / 6 | |
| 2.10.3 | 11 / 6 | |
| 2.10.2 | 11 / 6 | |
| 2.10.1 | 11 / 6 | |
| 2.10.0 | 11 / 6 | |
| 2.9.3 | 11 / 6 | |
| 2.9.2 | 10 / 6 | |
| 2.9.1 | 10 / 6 | |
| 2.9.0 | 10 / 6 | |
| 2.8.0 | 8 / 6 | |
| 2.7.2 | 7 / 5 | |
| 2.7.1 | 7 / 5 | |
| 2.7.0 | 7 / 5 | |
| 2.6.0 | 7 / 5 |
v2.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.3
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.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.
v2.8.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.
v2.7.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.
v2.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.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.
v2.6.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.