@authhero/saml
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:oslo | AI (phantom-deps): oslo is declared and used in SAML authentication logic; stable false positive. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): nanoid is declared and used for ID generation; stable false positive. | ai | |
| phantom-deps | phantom-dep:fast-xml-parser | AI (phantom-deps): fast-xml-parser is declared and core to SAML XML parsing; stable false positive. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.4.8 | 3 / 7 | |
| 0.4.7 | 3 / 7 | |
| 0.4.6 | 3 / 7 | |
| 0.4.5 | 3 / 7 | |
| 0.4.4 | 3 / 7 | |
| 0.4.3 | 3 / 7 | |
| 0.4.2 | 3 / 7 | |
| 0.4.1 | 3 / 6 | |
| 0.4.0 | 3 / 6 | |
| 0.3.0 | 3 / 6 | |
| 0.2.0 | 3 / 6 | |
| 0.1.55 | 2 / 6 | |
| 0.1.54 | 2 / 6 | |
| 0.1.53 | 2 / 6 | |
| 0.1.51 | 2 / 6 | |
| 0.1.50 | 2 / 6 | |
| 0.1.49 | 2 / 6 | |
| 0.1.48 | 2 / 6 | |
| 0.1.47 | 2 / 6 | |
| 0.1.46 | 2 / 6 |
v0.4.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.