@notion-kit/auth-ui
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@notion-kit/spinner | AI (dependencies): Same-monorepo sibling dep from trusted publisher steeeee0223; consistent versioning pattern. | ai | |
| dependencies | unvetted-dep:@notion-kit/settings-panel | AI (dependencies): Same-monorepo sibling dep from trusted publisher steeeee0223; consistent versioning pattern. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 8 / 10 | |
| 0.17.0 | 11 / 10 | |
| 0.16.0 | 11 / 10 | |
| 0.15.1 | 11 / 10 | |
| 0.15.0 | 11 / 10 | |
| 0.11.0 | 13 / 9 | |
| 0.10.0 | 13 / 9 |
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.