rc-notification
notification ui component for react
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/rc-notification.js | AI (source-diff): Standard webpack UMD bundle; 'network+exec' is false positive from webpack boilerplate patterns. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Major version bump added dist/ bundles and compiled output; size increase is expected. | ai | |
| source-diff | net-exec-file:dist/rc-notification.min.js | AI (source-diff): Minified webpack UMD bundle; same false positive as the non-minified version. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): yiminghe's removal is part of the long-standing Ant Design team transition for the react-component org. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Ant Design team (benjycui, afc163, zombiej, madccc) legitimately maintains the react-component org; yiminghe was the original creator who handed off. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): All added maintainers are established Ant Design team members with extensive npm track records. | ai | |
| — | publisher-changed | — | sean | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps rc-animate and rc-util are canonical react-component ecosystem packages from the same org/maintainer; not a supply-chain risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 2.3M weekly downloads published long before Sigstore provenance was available on npm. Absence is expected and not a risk signal here. | ai | |
| dependencies | unvetted-dep:rc-animate | AI (dependencies): rc-animate is a sibling react-component org package, a standard and expected dependency for this UI component. Not a security concern. | ai |
Versions (showing 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 5.6.4 | 4 / 24 | |
| 5.6.3 | 4 / 24 | |
| 5.6.2 | 4 / 24 | |
| 5.6.1 | 4 / 24 | |
| 5.6.0 | 4 / 24 | |
| 5.5.0 | 4 / 24 | |
| 5.4.0 | 4 / 24 | |
| 5.3.0 | 4 / 24 | |
| 5.2.0 | 4 / 24 | |
| 5.1.1 | 4 / 24 | |
| 5.1.0 | 4 / 24 | |
| 5.0.5 | 4 / 19 | |
| 5.0.4 | 4 / 19 | |
| 5.0.3 | 4 / 19 | |
| 5.0.2 | 4 / 19 | |
| 5.0.1 | 4 / 19 | |
| 5.0.0 | 4 / 19 | |
| 4.6.1 | 4 / 19 | |
| 4.6.0 | 4 / 19 | |
| 4.5.7 | 4 / 17 | |
| 4.5.6 | 4 / 17 | |
| 4.5.5 | 4 / 15 | |
| 4.5.4 | 4 / 15 | |
| 4.5.3 | 4 / 15 | |
| 4.5.2 | 4 / 15 | |
| 4.5.1 | 4 / 15 | |
| 4.5.0 | 4 / 14 | |
| 4.4.0 | 4 / 14 | |
| 4.3.2 | 3 / 14 | |
| 4.3.0 | 3 / 14 | |
| 4.0.0 | 3 / 12 | |
| 3.3.1 | 5 / 7 | |
| 3.3.0 | 5 / 7 | |
| 3.2.0 | 5 / 7 | |
| 3.1.1 | 5 / 7 | |
| 3.1.0 | 5 / 7 | |
| 3.0.1 | 5 / 7 | |
| 3.0.0 | 5 / 7 | |
| 2.0.6 | 5 / 6 | |
| 2.0.5 | 5 / 6 | |
| 2.0.4 | 5 / 6 | |
| 2.0.3 | 5 / 6 | |
| 2.0.2 | 5 / 6 | |
| 2.0.1 | 5 / 6 | |
| 2.0.0 | 5 / 6 | |
| 1.4.3 | 5 / 5 | |
| 1.4.2 | 4 / 5 | |
| 1.4.1 | 3 / 6 | |
| 1.4.0 | 3 / 6 | |
| 1.3.6 | 3 / 6 | |
| 1.3.5 | 3 / 6 | |
| 1.3.4 | 3 / 6 | |
| 1.3.3 | 3 / 6 | |
| 1.3.2 | 3 / 7 | |
| 1.3.1 | 3 / 7 | |
| 1.3.0 | 2 / 7 | |
| 1.2.0 | 2 / 7 | |
| 1.1.0 | 2 / 5 | |
| 1.0.1 | 1 / 5 | |
| 1.0.0 | 1 / 5 |
v4.4.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (afc163) than the most recent previously approved version (zombiej) on 2020-05-29, but afc163 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.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-08. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-10-18. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yesmeck) than the most recent previously approved version (nikogu) on 2018-07-30, but yesmeck 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.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yesmeck) than the most recent previously approved version (nikogu) on 2018-04-16, but yesmeck 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.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-01-11. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-10-10. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-09-15. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paranoidjk) than the most recent previously approved version (afc163) on 2017-07-31, but paranoidjk 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.
v2.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (afc163) than the most recent previously approved version (paranoidjk) on 2017-07-07, but afc163 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.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paranoidjk) than the most recent previously approved version (afc163) on 2017-06-01, but paranoidjk 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.
v1.4.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (paranoidjk) than the most recent previously approved version (afc163) on 2017-05-18, but paranoidjk 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.
v1.4.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (afc163) than the most recent previously approved version (yiminghe) on 2017-04-27, but afc163 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.
v1.4.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-03-13. This could indicate a legitimate maintainer transition or an account compromise.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.