@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, 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 |
|---|---|---|---|---|
| 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 100 of 132)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 4 / 2 | |
| 1.0.31 | 4 / 2 | |
| 1.0.30 | 4 / 2 | |
| 1.0.29 | 4 / 2 | |
| 1.0.28 | 4 / 2 | |
| 1.0.27 | 4 / 2 | |
| 1.0.26 | 4 / 2 | |
| 1.0.25 | 4 / 2 | |
| 1.0.24 | 4 / 2 | |
| 1.0.23 | 4 / 2 | |
| 1.0.22 | 4 / 2 | |
| 1.0.21 | 4 / 2 | |
| 1.0.20 | 4 / 2 | |
| 1.0.19 | 4 / 2 | |
| 1.0.18 | 4 / 2 | |
| 1.0.17 | 4 / 2 | |
| 1.0.16 | 4 / 2 | |
| 1.0.15 | 4 / 2 | |
| 1.0.14 | 4 / 2 | |
| 1.0.13 | 4 / 2 | |
| 1.0.12 | 4 / 2 | |
| 1.0.11 | 4 / 2 | |
| 1.0.10 | 4 / 2 | |
| 1.0.9 | 4 / 2 | |
| 1.0.8 | 4 / 2 | |
| 1.0.7 | 4 / 2 | |
| 1.0.6 | 4 / 2 | |
| 1.0.5 | 4 / 2 | |
| 1.0.4 | 5 / 2 | |
| 1.0.3 | 5 / 2 | |
| 1.0.2 | 5 / 2 | |
| 1.0.1 | 5 / 2 | |
| 1.0.0 | 5 / 2 | |
| 0.4.55 | 5 / 2 | |
| 0.4.54 | 5 / 2 | |
| 0.4.53 | 5 / 2 | |
| 0.4.52 | 5 / 2 | |
| 0.4.51 | 5 / 2 | |
| 0.4.50 | 5 / 2 | |
| 0.4.47 | 5 / 2 | |
| 0.4.46 | 5 / 2 | |
| 0.4.45 | 5 / 2 | |
| 0.4.44 | 5 / 2 | |
| 0.4.43 | 5 / 2 | |
| 0.4.42 | 5 / 2 | |
| 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 | |
| 0.3.23 | 5 / 0 | |
| 0.3.22 | 5 / 0 | |
| 0.3.21 | 5 / 0 | |
| 0.3.20 | 5 / 0 |
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.