@girder/girder-plugin-oauth
Allow users to login via supported OAuth2 providers.
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@girder/core | AI (npm-metadata): file: path is a monorepo-internal build-time reference; published package ships pre-built dist, so it poses no runtime registry-bypass risk. | ai | |
| dependencies | unvetted-dep:@girder/core | AI (dependencies): Same monorepo file: dep; not a real registry dependency, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@girder/core | AI (phantom-deps): Same-org monorepo dep bundled into dist; not directly imported in source is expected for a pre-built plugin. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.0.10 | 1 / 4 | |
| 5.0.9 | 1 / 4 | |
| 5.0.8 | 1 / 4 | |
| 5.0.7 | 1 / 4 | |
| 5.0.6 | 1 / 4 | |
| 5.0.5 | 1 / 4 | |
| 5.0.4 | 1 / 4 | |
| 5.0.3 | 1 / 4 | |
| 5.0.2 | 1 / 4 | |
| 5.0.1 | 1 / 4 | |
| 5.0.0 | 1 / 4 |
v5.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.