@checkstack/auth-saml-backend
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 | no-description | AI (npm-metadata): Internal monorepo plugin; sparse metadata is expected for private org packages. | ai | |
| license | uncommon-license:Elastic-2.0 | AI (license): Elastic-2.0 is a known source-available license; stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; no other risk signals present. | ai | |
| provenance | missing-githead | AI (provenance): Consistent @checkstack org publisher across 25 versions; missing gitHead appears to be a build environment change, not a supply-chain indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @checkstack ecosystem package; sparse metadata is consistent across the org, not a spam/malware indicator. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.2.5 | 7 / 3 | |
| 0.2.4 | 7 / 3 | |
| 0.2.3 | 7 / 3 | |
| 0.2.2 | 7 / 3 | |
| 0.2.1 | 7 / 3 | |
| 0.2.0 | 7 / 3 | |
| 0.1.33 | 7 / 3 | |
| 0.1.32 | 7 / 3 | |
| 0.1.31 | 7 / 3 | |
| 0.1.30 | 7 / 3 | |
| 0.1.29 | 7 / 3 | |
| 0.1.28 | 7 / 3 | |
| 0.1.27 | 7 / 3 | |
| 0.1.26 | 7 / 3 | |
| 0.1.25 | 7 / 3 | |
| 0.1.24 | 7 / 3 | |
| 0.1.23 | 7 / 3 | |
| 0.1.20 | 7 / 3 | |
| 0.1.19 | 7 / 3 | |
| 0.1.16 | 7 / 3 | |
| 0.1.15 | 7 / 3 | |
| 0.1.14 | 7 / 3 | |
| 0.1.13 | 7 / 3 | |
| 0.1.12 | 7 / 3 | |
| 0.1.10 | 7 / 3 | |
| 0.1.9 | 7 / 3 | |
| 0.1.8 | 7 / 3 | |
| 0.1.7 | 7 / 3 | |
| 0.1.5 | 7 / 3 | |
| 0.1.4 | 7 / 3 | |
| 0.1.3 | 7 / 3 | |
| 0.1.2 | 7 / 3 | |
| 0.1.1 | 7 / 3 | |
| 0.1.0 | 7 / 3 |
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
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: enyineer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
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: enyineer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: enyineer.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.