@syntrologie/adapt-content
Adaptive Content app - DOM manipulation actions for text, attributes, and styles
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Both new deps are legitimate: css-selector-generator is a well-known utility, and @syntrologie/shared-editor-ui is an internal same-org package consistent with this SDK's purpose. | ai | |
| phantom-deps | phantom-dep:data-urls | AI (phantom-deps): data-urls is explicitly declared in dependencies and legitimately used; static analysis false positive. | ai | |
| dependencies | unvetted-dep:css-selector-generator | AI (dependencies): css-selector-generator is a well-known, legitimate npm package for CSS selector generation; not a security risk for this package. | ai | |
| dependencies | unvetted-dep:@syntrologie/shared-editor-ui | AI (dependencies): Internal scoped package from the same Syntrologie org, bundled via bundledDependencies — standard monorepo pattern, not a third-party risk. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.28.0 | 2 / 5 | |
| 2.27.0 | 2 / 5 | |
| 2.26.0 | 2 / 5 | |
| 2.25.2 | 2 / 5 | |
| 2.25.1 | 2 / 5 | |
| 2.25.0 | 2 / 5 | |
| 2.24.3 | 2 / 5 | |
| 2.24.2 | 2 / 5 | |
| 2.24.1 | 2 / 5 | |
| 2.24.0 | 2 / 5 | |
| 2.23.0 | 2 / 5 | |
| 2.22.0 | 2 / 5 | |
| 2.21.0 | 2 / 5 | |
| 2.20.0 | 2 / 5 | |
| 2.19.0 | 2 / 5 | |
| 2.18.0 | 2 / 5 | |
| 2.17.0 | 2 / 5 | |
| 2.16.0 | 3 / 12 | |
| 2.14.0 | 3 / 12 | |
| 2.13.0 | 3 / 12 | |
| 2.12.0 | 3 / 12 | |
| 2.1.0 | 2 / 11 | |
| 2.0.1 | 0 / 10 | |
| 1.0.0 | 0 / 10 |
v2.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.