@atlaskit/adf-schema
Shared package that contains the ADF-schema (json) and ProseMirror node/mark specs
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Atlassian publishes via internal artifact pipeline; missing gitHead is consistent with their known publish environment across @atlaskit packages. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian's internal publish pipeline does not use Sigstore provenance; stable for all @atlaskit packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Large Atlassian monorepo package; minimal README and no keywords are expected for internal/ecosystem packages of this scale and age. | ai |
Versions (showing 12 of 122)
| Version | Deps | Published |
|---|---|---|
| 51.5.10 | 7 / 35 | |
| 51.5.9 | 7 / 35 | |
| 51.5.8 | 7 / 35 | |
| 51.5.7 | 7 / 35 | |
| 51.5.6 | 8 / 35 | |
| 51.5.5 | 7 / 35 | |
| 51.5.4 | 8 / 34 | |
| 51.5.3 | 9 / 34 | |
| 51.5.2 | 9 / 34 | |
| 51.5.1 | 6 / 34 | |
| 51.5.0 | 6 / 34 | |
| 51.4.0 | 6 / 34 |
v51.5.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.5.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.5.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.5.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.5.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atlassianartifactteam.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v51.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.