@atlaskit/teams-app-internal-product-permissions
Fetches a user's product permissions, with support for permissions scoped to specific resources.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atlaskit/css | AI (phantom-deps): Declared dependency in same-org monorepo; phantom-dep pattern is expected for shared Atlassian packages. | ai | |
| phantom-deps | phantom-dep:@compiled/react | AI (phantom-deps): Declared dependency referenced in config; legitimate monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Declared dependency in same-org monorepo; expected pattern for Atlassian packages. | ai | |
| phantom-deps | phantom-dep:@atlaskit/primitives | AI (phantom-deps): Declared dependency in same-org monorepo; stable pattern for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 3 / 6 | |
| 1.3.1 | 3 / 6 | |
| 1.3.0 | 3 / 5 | |
| 1.2.9 | 6 / 6 | |
| 1.2.8 | 6 / 6 | |
| 1.2.7 | 6 / 6 | |
| 1.2.6 | 6 / 6 | |
| 1.2.5 | 6 / 6 | |
| 1.2.4 | 6 / 6 | |
| 1.2.3 | 6 / 6 | |
| 1.2.2 | 6 / 6 | |
| 1.2.1 | 6 / 7 | |
| 1.2.0 | 6 / 7 | |
| 1.1.1 | 6 / 8 | |
| 1.1.0 | 6 / 8 | |
| 1.0.0 | 6 / 8 |
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.