← Home

@imj_media/loginsso

npm Homepage

SSO Login

12
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

renecarrilloimjmediamariaayalaolafruvalcabaoscar_rubio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:uuid AI (phantom-deps): Declared as both dependency and peerDependency; phantom detection is a false positive for this package. ai
phantom-deps phantom-dep:axios AI (phantom-deps): Declared as both dependency and peerDependency; phantom detection is a false positive for this package. ai
phantom-deps phantom-dep:crypto-es AI (phantom-deps): Declared as both dependency and peerDependency; phantom detection is a false positive for this package. ai
phantom-deps phantom-dep:crypto-js AI (phantom-deps): Declared as both dependency and peerDependency; phantom detection is a false positive for this package. ai
phantom-deps phantom-dep:react-shadow AI (phantom-deps): Declared as runtime dependency; phantom detection is a false positive for this package. ai
phantom-deps phantom-dep:storybook-addon-react-docgen AI (phantom-deps): Storybook tooling dependency; phantom detection is a false positive for this package. ai
phantom-deps phantom-dep:@fortawesome/pro-regular-svg-icons AI (phantom-deps): UI icon dependency; phantom detection is a false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
3.6.0 7 / 14
3.5.0 7 / 13
3.3.3 5 / 12
3.3.2 5 / 12
3.3.1 5 / 12
3.2.28 5 / 12
3.2.27 5 / 12
3.2.26 5 / 12
3.2.25 5 / 12
3.2.24 5 / 12
3.2.23 5 / 12
3.2.22 5 / 12

v3.3.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: azazelimj → victorgalvan (on 2024-12-18, known maintainer) provenance

This version was published by a different npm account (victorgalvan) than the most recent previously approved version (azazelimj) on 2024-12-18, but victorgalvan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.3.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: imjmedia → azazelimj (on 2024-09-17, known maintainer) provenance

This version was published by a different npm account (azazelimj) than the most recent previously approved version (imjmedia) on 2024-09-17, but azazelimj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.3.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: victorgalvan → imjmedia (on 2024-09-10, known maintainer) provenance

This version was published by a different npm account (imjmedia) than the most recent previously approved version (victorgalvan) on 2024-09-10, but imjmedia is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.2.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.26

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: renecarrillo → victorgalvan (on 2024-06-19, known maintainer) provenance

This version was published by a different npm account (victorgalvan) than the most recent previously approved version (renecarrillo) on 2024-06-19, but victorgalvan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.2.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.