@syntrologie/adapt-nav
Adaptive Navigation - Nav link widget, scroll-to and page navigation actions
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 | rapid-publish | AI (publish-pattern): High-velocity monorepo with 366 versions; automated CI publishing is the expected pattern here. | ai | |
| phantom-deps | phantom-dep:@syntro/design-system | AI (phantom-deps): Declared in bundledDependencies; phantom-dep is expected for bundled deps. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party Syntrologie/Syntro packages consistent with the org's SDK ecosystem; no malicious indicators present. | ai | |
| dependencies | unvetted-dep:@syntro/design-system | AI (dependencies): First-party Syntrologie design system, bundled as an internal dependency in a monorepo pattern. Not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@syntrologie/sdk-contracts | AI (dependencies): First-party Syntrologie package, bundled as an internal sibling dependency in a monorepo pattern. | ai | |
| dependencies | unvetted-dep:@syntrologie/shared-editor-ui | AI (dependencies): First-party Syntrologie package, bundled as an internal sibling dependency in a monorepo pattern. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.25.1 | 3 / 10 | |
| 2.25.0 | 3 / 10 | |
| 2.24.3 | 3 / 10 | |
| 2.24.2 | 3 / 10 | |
| 2.24.1 | 3 / 10 | |
| 2.24.0 | 3 / 10 | |
| 2.21.0 | 3 / 10 | |
| 2.20.0 | 3 / 10 | |
| 2.19.0 | 3 / 10 | |
| 2.16.0 | 3 / 11 | |
| 2.15.0 | 3 / 11 | |
| 2.12.0 | 3 / 8 | |
| 2.1.0 | 2 / 8 | |
| 2.0.1 | 0 / 9 | |
| 1.0.0 | 0 / 9 |
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.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.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.