@atlaskit/insm
INSM tooling measures user-perceived interactivity of a page
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Atlassian monorepo packages routinely publish at 0.0.0 as initial/placeholder versions; not a malware signal for this publisher. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Build-time transitive dep in Atlassian monorepo; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tmp-editor-statsig | AI (phantom-deps): Same-org monorepo dep; loaded by convention, not a direct import concern. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes @atlaskit packages from their monorepo without Sigstore provenance; this is consistent across their entire package ecosystem and not a risk signal. | ai |
Versions (showing 51 of 87)
| Version | Deps | Published |
|---|---|---|
| 0.4.41 | 5 / 2 | |
| 0.4.40 | 5 / 2 | |
| 0.4.39 | 5 / 2 | |
| 0.4.38 | 5 / 2 | |
| 0.4.37 | 5 / 2 | |
| 0.4.36 | 5 / 2 | |
| 0.4.35 | 5 / 2 | |
| 0.4.34 | 5 / 1 | |
| 0.4.33 | 5 / 1 | |
| 0.4.32 | 5 / 1 | |
| 0.4.31 | 5 / 1 | |
| 0.4.30 | 5 / 1 | |
| 0.4.29 | 5 / 1 | |
| 0.4.28 | 5 / 1 | |
| 0.4.27 | 5 / 1 | |
| 0.4.26 | 5 / 1 | |
| 0.4.25 | 5 / 1 | |
| 0.4.24 | 5 / 0 | |
| 0.4.23 | 5 / 0 | |
| 0.4.22 | 5 / 0 | |
| 0.4.21 | 5 / 0 | |
| 0.4.20 | 5 / 0 | |
| 0.4.19 | 5 / 0 | |
| 0.4.18 | 5 / 0 | |
| 0.4.17 | 5 / 0 | |
| 0.4.16 | 5 / 0 | |
| 0.4.15 | 5 / 0 | |
| 0.4.14 | 5 / 0 | |
| 0.4.13 | 5 / 0 | |
| 0.4.12 | 5 / 0 | |
| 0.4.11 | 5 / 0 | |
| 0.4.10 | 5 / 0 | |
| 0.4.9 | 5 / 0 | |
| 0.4.8 | 5 / 0 | |
| 0.4.7 | 5 / 0 | |
| 0.4.6 | 5 / 0 | |
| 0.4.5 | 5 / 0 | |
| 0.4.4 | 5 / 0 | |
| 0.4.3 | 5 / 0 | |
| 0.4.2 | 5 / 0 | |
| 0.4.1 | 5 / 0 | |
| 0.4.0 | 5 / 0 | |
| 0.3.32 | 5 / 0 | |
| 0.3.31 | 5 / 0 | |
| 0.3.30 | 5 / 0 | |
| 0.3.29 | 5 / 0 | |
| 0.3.28 | 5 / 0 | |
| 0.3.27 | 5 / 0 | |
| 0.3.26 | 5 / 0 | |
| 0.3.25 | 5 / 0 | |
| 0.3.24 | 5 / 0 |
v0.4.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
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.4.6
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.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
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.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
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.3.31
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.3.30
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.3.29
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.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.